<!-- source: openspec/_root/INDEX.md -->

# Capability index

> Auto-generated from frontmatter of every `openspec/current/**/*.md` file.
> Do NOT edit by hand — run `node tools/build-openspec-index.mjs` to regenerate.

## Agents Overview
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Source of truth for the orchestra — six agent identities, roles, Cast names, storage ownership, communication graph, and activation phases.
Path: `current/agents-overview.md`

## Auth
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Magic-link authentication and middleware-enforced sessions for studio workspace. Built on Supabase Auth with RLS and role enforcement.
Path: `current/auth.md`

## Canvas
Status: deprecated. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Deprecated 2026-05-03. The Canvas v2 React Flow visualization vision is superseded by the Mirror perceptual spec layer.
Path: `current/canvas.md`

## cli-core
Status: stable. Audience: architect, executor, reviewer. Owner: pavel.
TLDR: Shared library for the CLI orchestra — events, LLM wrapping, lineage, context, auth, and citty conventions. One import; all three CLIs.
Path: `current/cli-core.md`

## Config
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Type-safe zod-validated environment and per-vendor accessors. Leaf package; consumed by db and auth, transitively by both apps.
Path: `current/config.md`

## DB — Conventions
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Conventions for the db package — browser singleton vs admin factory, file naming, barrel-only index, and no-business-logic rule.
Path: `current/db/conventions.md`

## DB — Entities
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: All schema entities owned by the db Supabase project — canvas tables, user_settings, leads, RPCs, and every applied amendment.
Path: `current/db/entities.md`

## DB — Modules
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Module map for the db package — which source files export client, admin, types, and the barrel index, and who consumes them.
Path: `current/db/modules.md`

## DB — Narrative
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Architecture rationale for the db package — why it exists, browser/admin client separation philosophy, and open questions.
Path: `current/db/narrative.md`

## DB — Overview
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Routing surface for the db capability — thin Supabase client wrappers (browser singleton, admin factory) plus a typed Database shape.
Path: `current/db/README.md`

## DB — Spec
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Engineering contract for the db package — package location, browser/admin separation, RLS contract, dependencies, and known gaps.
Path: `current/db/spec.md`

## DB — Types
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Database type shape for the db package — generation rules, table and RPC inventory, regeneration steps, and TypeScript conventions.
Path: `current/db/types.md`

## Design Components
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Component-intent spec for the studio design system — per-primitive anatomy, closed variant lists with rationale, a11y baseline, status, and the R10 promotion criteria.
Path: `current/design-components.md`

## Design Motion
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Motion spec for the studio design system — duration scale, easing curves, motion modes, the duration-scalar reduced-motion mechanism, and choreography rules.
Path: `current/design-motion.md`

## Design System
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Umbrella visual-intent spec for the studio design system — philosophy, voice, surface mapping, hard constraints, and the studio-wide WCAG 2.2 AA accessibility contract.
Path: `current/design-system.md`

## Design Tokens
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Token registry for the studio design system — each row carries a W3C DTCG type tag, semantic role, Tailwind utility, and mode parity.
Path: `current/design-tokens.md`

## Entity catalog
Status: stable. Audience: pavel, architect, executor. Owner: pavel.
TLDR: Complete ordered list of nouns the studio refers to. Four tiers (1, 2, infra, external); Tier-1 entities get the full five-density EntityCard treatment. Ratifies D-ATLAS-6.
Path: `current/entities.md`
Related: openspec/current/entity-densities.md, openspec/current/status-resolver.md, openspec/brands/studio/entities/_index.md, openspec/_atlas/current/atlas.html

## Entity densities — the five-density grammar
Status: stable. Audience: pavel, architect, executor. Owner: pavel.
TLDR: Every entity renders in exactly five densities — mention, row, card, hovercard, detail. The variant decides geometry, the entity decides content. Ratifies D-ATLAS-1.
Path: `current/entity-densities.md`
Related: openspec/current/entities.md, openspec/brands/studio/design-components.md, openspec/_atlas/current/atlas.html

## Forge — Audit watchman and calibration falsifier
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Capability spec for the OpenSpec audit calibration watchman — thresholds, event schemas, and falsifier semantics.
Path: `current/forge-audit.md`

## Forge — Commands
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Per-command reference for Forge — all command definitions plus review orchestration agents, finding schema, verifier, and cost guard.
Path: `current/forge/commands.md`

## Forge — Entities
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Data structures for Forge — Builder mode identity model, module registry, persistence, convention adapters, reports, and UI entities.
Path: `current/forge/entities.md`

## Forge — Narrative
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Positioning context for Forge — why it exists, status, where it lives, distribution, and related-capability cross-references.
Path: `current/forge/narrative.md`

## Forge — Overview
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Routing surface for the forge capability — project-agnostic CLI engine for Linear-driven autonomous code pipelines.
Path: `current/forge/README.md`

## Forge — Spec
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Engineering contract for Forge — architecture, configuration, multi-project routing, required env vars, dependencies, and boundaries.
Path: `current/forge/spec.md`

## Forge — Verifier
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Verification contract for forge build — five checkpoint gates, build outcome enum, failure modes, retry policy, and known gaps.
Path: `current/forge/verifier.md`

## Forms
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Standard for every form in the studio — nine binding rules covering validation timing, error anatomy, accessibility, and discard guards.
Path: `current/forms.md`

## Frontend Runtime
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: The contract every studio UI satisfies so users perceive instant navigation, live data, and zero loading flashes. SPA-feel as a goal.
Path: `current/frontend-runtime.md`

## Home — Block Contracts
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Full per-block contracts for the homepage — Nav through Footer plus amendment deltas, with purpose, content, and visual rules each.
Path: `current/home/blocks.md`

## Home — Entities
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Local data entities for the homepage — work card MDX, lab post MDX, and network person frontmatter contracts.
Path: `current/home/entities.md`

## Home — Flows
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Page narrative arc for the homepage — visitor flow through all blocks, audience tagging, and persona-to-block separation invariants.
Path: `current/home/flows.md`

## Home — Narrative
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Why the homepage exists and what it is — the top-of-funnel conversion surface, its block arc, and related capabilities.
Path: `current/home/narrative.md`

## Home — Overview
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Routing surface for the home capability — per-block contracts for the marketing homepage at the public site root.
Path: `current/home/README.md`

## Home — Spec
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Block template structure and cross-reference map for the homepage — the eleven-section anchor template and spec-governance conventions.
Path: `current/home/spec.md`

## Home — Typography
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Cross-block audience tag system for the homepage — the Chip skill component used across ForFounders and WhoWeWorkWith.
Path: `current/home/typography.md`

## i18n
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Thin wrapper around next-intl — routing config, navigation helpers, and per-locale message catalogs (en, ru, ro). Consumed by apps/web.
Path: `current/i18n.md`

## Linkable UI
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: URL-state overlay system — every meaningful UI state is encoded in the URL. Owns URL grammar, OverlayHost and DialogModule contracts.
Path: `current/linkable-ui.md`

## Maestro
Status: proposed. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Capability spec for the Maestro agent — routes work between agents, audits cross-agent state, surfaces decision points to Pavel. Substrate-pending.
Path: `current/agents/maestro.md`

## Muse
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: The AI substrate — one personality, four modes (Canvas, Scout, Architect, Builder). Architect and Builder modes active in v1.
Path: `current/muse.md`

## Muse (CLI agent)
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Capability spec for the muse CLI binary — turns Linear issues into OpenSpec change proposals via the draft command.
Path: `current/agents/muse.md`

## Muse Research
Status: stable. Audience: founder, executor. Owner: pavel.
TLDR: The muse research subcommand family turns a falsifiable thesis into a structured Inquiry — a multi-stream desk-research artifact with promoted Findings.
Path: `current/muse/research.md`

## Platform
Status: stable. Audience: pavel, ai, engineer, architect, founder. Owner: pavel.
TLDR: Rapoport Studio corporate platform — web, studio workspace, Forge CLI, Muse AI, Canvas. Spec-driven operating model.
Path: `current/platform.md`

## Robot operator surface platform
Status: proposed. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Three-layer architecture for bespoke robot operator surfaces — Gateway adapters, branded UI Shell, AI-Companion layer. Project engagements, not SaaS. Deferred pending pilot evidence.
Path: `current/robot-operator.md`

## Spec preview
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: In-canvas projection of an in-flight openspec change. Snapshots `canvas_files` and renders affected `openspec/current/*.md` capabilities alongside drafted excerpts when `?view=preview`.
Path: `current/spec-preview.md`

## State
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: XState v5 state-machine library — owns workflow modeling, Realtime integration, Server Action lifecycle, and persistence helpers.
Path: `current/state.md`

## Status resolver — six visual roles
Status: stable. Audience: pavel, architect, executor. Owner: pavel.
TLDR: One pill, one resolver, one taxonomy. Every studio status string resolves to one of six visual roles — live, progressing, idle, archived, error, embargo. Ratifies D-ATLAS-2/3.
Path: `current/status-resolver.md`
Related: openspec/current/entity-densities.md, openspec/brands/studio/design-tokens.md, openspec/brands/studio/design-components.md, openspec/_atlas/current/atlas.html

## Studio
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Auth-walled workspace at app.rapoport.studio — admin surfaces for managing the studio operations, content, and infrastructure.
Path: `current/studio.md`

## Studio Workspace — Entities
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Local data entities for the workspace — CanvasSession, UserSettings, and more. Cross-references db for canonical schema.
Path: `current/studio-workspace/entities.md`

## Studio Workspace — Flows
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Sequenced user flows for the workspace — authoring loop, canvas creation, settings entry, and sidebar navigation.
Path: `current/studio-workspace/flows.md`

## Studio Workspace — Narrative
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Why the workspace exists and who it serves — the v1 Architect-mode authoring surface and the v2 out-of-scope fence.
Path: `current/studio-workspace/narrative.md`

## Studio Workspace — Overview
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Routing surface for the studio-workspace capability — the auth-walled internal workspace at app.rapoport.studio.
Path: `current/studio-workspace/README.md`

## Studio Workspace — Spec
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Behavioural contracts for the workspace — surface area, route tables, API endpoints, and all applied amendments.
Path: `current/studio-workspace/spec.md`

## Telegram
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Telegram surfaces operated by the studio — three tiers, two bots, one shared n8n bridge. Per-canvas group is the primary work surface.
Path: `current/telegram.md`

## UI
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Implementation package for the design system — tokens, primitives, blocks, and animations as React and Tailwind components.
Path: `current/ui.md`

## Web
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: Public marketing site at rapoport.studio — sells the studio curation model and AI-orchestration thesis; intakes new projects.
Path: `current/web.md`

## Workflow
Status: stable. Audience: pavel, ai, engineer. Owner: pavel.
TLDR: The eleven-stage operating timeline for all work at the studio — every change moves from raw idea to live release along this timeline.
Path: `current/workflow.md`
