Repositories
Where each piece lives and what it owns.
The code lives across several GitHub repos under the conclavehq org, mirrored as working dirs in
the shape-rotator-all monorepo used for local development.
| GitHub repo | Local dir | Owns |
|---|---|---|
conclavehq/Conclave | conclave-shape-rotator/ | Intelligence + control plane, persistence, frontend |
conclavehq/Capture | capture/ | Meeting capture + diarization (identity-free) |
conclavehq/VFTEE | FPM/ | Voice identity + consent plane |
conclavehq/Mobile | conclave-mobile/ | React Native / Expo app |
conclavehq/Veritas | veritas-recorder/ | Standalone attested recorder (satellite) |
conclavehq/Sync | — | The umbrella / capture engine lineage |
What each repo contains
- Conclave — FastAPI backend (
api/,connectors/,infra/,transcripts/,storage/), Alembic migrations (alembic/), and the Next.js dashboard infrontend/. - Capture — the diarization service (
services/diarization/), the Node recato-bot (services/recato-bot/), and the runtime-api orchestrator. Dockerfiles.diart/.gpu. - VFTE / FPM — the identity service (
fpm/), the sealed SQLite store, the Ed25519 signers, and the Next.js consent dashboard.
Boundary reminder: only Conclave persists content. Capture holds nothing; VFTE holds voiceprints + consent edges but never audio or transcript. See Architecture.
Branch & merge conventions
Work happens on one feat/<slug> branch (often a dedicated git worktree) per task per repo. A change
lands on main only after a green test gate, an independent mutation audit, and explicit approval —
and pushes are human-run. Many features are therefore merged locally but not yet pushed; the
Status board tracks which. Full workflow:
Build workflow.
Source: per-repo READMEs, task-plan/MASTER-TASK-LIST.md.