For agents
How an AI agent should read this repo and where the source of truth lives.
This site is built to be consumed by agents as much as by people. If you were pointed here to understand Conclave or to contribute, read this first.
Fastest way to load the whole thing
/llms.txt— a compact index of every page with links./llms-full.txt— the entire documentation corpus as one plain-text document. Fetch this when you want everything in one shot./llms.mdx/docs/<slug>/content.md— any single page as clean Markdown. Every page also has a Copy as Markdown button in its header.- The raw source is plain MDX under
content/docs/— read it directly from the repo.
Reading order
indexandproduct/overview— the three products (Conclave / Capture / VFTE) and the boundary between them.product/trust-model+product/concepts/*— operator-blindness, voiceprints, the consent plane, workspaces, diarization, the knowledge graph.engineering/architecture+engineering/data-flow— topology and how a meeting flows end to end.engineering/status(what's built) thenengineering/roadmap(what's not).- Dive into
product/features/*orengineering/reference/*for the specific surface you're touching.
The source-of-truth map
These docs summarize and link to the canonical specs, which live in the upstream
shape-rotator-all/ monorepo. When a status claim matters, verify against the source:
| Topic | Canonical source |
|---|---|
| Every feature, all three products | FEATURE-SPEC.md |
| Trust / scoping / consent grammar | discoveries/WORKSPACES-AND-VFT-GRAMMAR.md, FPM/CONSENT-PLANE.md |
| Architecture & data flow | CONCLAVE-CAPTURE-ARCHITECTURE.md, DIARIZATION-MIGRATION.md |
| Deployment, CVMs, gotchas | DEPLOYMENT-GUIDE.md, ENVIRONMENTS.md |
| What's built (status) | task-plan/MASTER-TASK-LIST.md |
| What's planned (backlog) | live GitHub issues in conclavehq/{Conclave,Capture,VFTEE,Mobile} |
Rules if you write here
- Only document what is implemented. Ground truth for "shipped" is
Status +
MASTER-TASK-LIST.md; ground truth for "planned" is the live GitHub issue tracker. Never dress an open issue up as a shipped feature. - Attach an honest status badge to every feature:
Live in prod·Built · merged local·Built · not merged. Say built, not shipped, when it's local-only. - Surface known open bugs where relevant (e.g. the web login loop) — don't hide them.
- Match the house style in Writing docs: dense, cited, minimalist, no filler.
- Keep
npm run buildgreen.