Vibecodr – Concepts & Terminology

Concept Graph

Visual representation of how core concepts relate:

┌─────────────────────────────────────────────────────────────────────────────┐ │ USER-FACING CONCEPTS │ │ ┌──────────┐ contains ┌──────────┐ stored as ┌──────────────┐ │ │ │ Post │ ─────────────→ │ Vibe │ ─────────────→ │ Capsule │ │ │ └──────────┘ └──────────┘ └──────────────┘ │ │ │ │ │ │ │ │ appears in │ runs on │ compiles │ │ ▼ ▼ ▼ │ │ ┌──────────┐ ┌──────────┐ ┌──────────────┐ │ │ │ Feed │ │ Player │ │ Artifact │ │ │ └──────────┘ └──────────┘ └──────────────┘ │ │ │ │ │ │ calls via postMessage │ │ ▼ │ │ ┌──────────┐ bound to ┌──────────────┐ │ │ │ Pulse │ ─────────────→ │ Integration │ │ │ └──────────┘ └──────────────┘ │ │ │ │ │ │ executed via │ │ ▼ │ │ ┌──────────┐ │ │ │ Grant │ (30-90s TTL) │ │ └──────────┘ │ └─────────────────────────────────────────────────────────────────────────────┘ ┌─────────────────────────────────────────────────────────────────────────────┐ │ INFRASTRUCTURE CONCEPTS │ │ ┌──────────────┐ ┌──────────────┐ ┌──────────────────────┐ │ │ │ API Worker │ ─────→ │ Dispatch │ ─────→ │ WfP Pulse Workers │ │ │ │ (data ops) │ │ Worker │ │ (per-user isolates) │ │ │ └──────────────┘ └──────────────┘ └──────────────────────┘ │ │ │ │ │ │ reads/writes │ │ ▼ │ │ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │ │ │ D1 │ │ R2 │ │ KV │ │ DO │ │ │ │ (SQLite) │ │ (Storage) │ │ (Cache) │ │ (Stateful) │ │ │ └──────────────┘ └──────────────┘ └──────────────┘ └──────────────┘ │ └─────────────────────────────────────────────────────────────────────────────┘

Core Terms

Vibe user-facing

A self-contained web app that runs in the browser. The primary user-facing concept. Vibes appear in feeds, players, and embeds.

Related: stored as → Capsule | runs in → Player | attached to → Post | can fork via → Remix

Pulse user-facing

A server-side function that powers vibes. The only way for vibes to run trusted backend logic (e.g., API calls with secrets, database operations).

Related: called by → Vibe (via Grant) | uses → Integration | deployed on → WfP

Capsule internal

The internal data container holding a vibe's code and assets. Not user-facing terminology—users see "vibes."

Related: contains → Manifest | compiles to → Artifact | owned by → User

Artifact internal

A compiled runtime bundle for a capsule. Types: react-jsx, html, library. Served to the player iframe.

Related: compiled from → Capsule | loaded by → Player | has → Manifest

Integration user-facing

A configured connection to an external service (OpenAI, Supabase, Stripe, etc.). Holds encrypted secrets.

Related: used by → Pulse | accessed via → Proxy | stores → Secrets

Grant internal

A short-lived JWT (30-90s TTL) that authorizes a vibe to execute a specific pulse. Scoped to {userId, pulseId}.

Related: issued by → API Worker | validated by → Dispatch Worker | authorizes → Pulse Run

Recipe user-facing

A saved preset of parameter values for a vibe. Users can create and share recipes.

Related: belongs to → Capsule | saves → Params

Remix user-facing

Forking someone's vibe to make your own version. Creates a parent-child relationship.

Related: creates new → Capsule | links to → Parent Vibe

UI Surfaces

Studio user-facing

The creative workspace for building vibes. Code editor, file browser, preview panel.

Related: edits → Capsule | previews in → Player

Player user-facing

The full-screen execution environment for vibes. Displays the sandboxed iframe with runtime controls.

Related: loads → Artifact | hosts → Iframe | shows → Params

Feed user-facing

The social timeline showing posts and vibes. Modes: latest, following, foryou.

Related: contains → Posts | supports inline → Playback

Infrastructure Terms

WfP (Workers for Platforms) infrastructure

Cloudflare's multi-tenant worker hosting. Each pulse runs as an isolated WfP worker.

Related: hosts → Pulse Workers | managed by → Dispatch Worker

Dispatch Worker infrastructure

Routes requests to the correct user pulse worker. Validates grants, enforces rate limits.

Related: validates → Grant | routes to → Pulse Worker | enforces → Quotas

API Worker infrastructure

Main REST API handling all data operations. Talks to D1, R2, KV, and Durable Objects.

Related: serves → REST API | issues → Grants | manages → D1/R2/KV

Quick Lookup Table

Term	One-Line Definition	Type
Vibe	Client-side web app running in sandboxed iframe	User-facing
Pulse	Server-side function on WfP (edge workers)	User-facing
Capsule	Internal container for vibe code/assets	Internal
Artifact	Compiled bundle served to runtime	Internal
Integration	External service connection with encrypted secrets	User-facing
Grant	Short-lived JWT authorizing pulse execution	Internal
Recipe	Saved parameter preset for a vibe	User-facing
Remix	Fork of another user's vibe	User-facing
Studio	Code editor workspace for vibes	User-facing
Player	Full-screen vibe execution environment	User-facing
Trigger	Automation rule that fires on events	User-facing
WfP	Workers for Platforms (Cloudflare multi-tenant hosting)	Infrastructure