# Docs - [Conclave](/docs): Your team's confidential memory — every meeting, searchable, and even we can't read it. The reference for humans and agents. - Product - [The three products](/docs/product/overview): Conclave, Capture, and VFTE — one mental model for the whole system. - [Why Conclave](/docs/product/why-conclave): Confidential Team Memory — the empty quadrant, and why access is not privacy. - [Trust model](/docs/product/trust-model): Operator-blindness, TEE + TDX attestation, and "verify, don't trust". - **Concepts** - [Voiceprints](/docs/product/concepts/voiceprints): CAM++ 512-d voice embeddings, sealed and deterministic. - [The consent plane](/docs/product/concepts/consent-plane): allow / anonymous / denied, id visibility, and forget — consent lives at the microphone. - [Workspaces](/docs/product/concepts/workspaces): The trust boundary — two graphs, one boundary. - [Diarization](/docs/product/concepts/diarization): Who spoke when, anonymously — diart (live) and DiariZen (post-pass). - [Knowledge graph & search](/docs/product/concepts/knowledge-graph): Bi-temporal entities, hybrid BM25 + embedding retrieval, and Ask (RAG). - **Features** - [Conclave features](/docs/product/features/conclave): The intelligence and control plane — capture, editor, insights, KB, sharing, audio. - [Capture features](/docs/product/features/capture): Meeting capture and acoustic diarization — identity-free by design. - [VFTE features](/docs/product/features/vfte): Voice identity and the consent layer — enroll, identify, deletion proof. - [VFTE as a service](/docs/product/vftee-as-a-service): A voice you own — the standalone identity + consent API thesis. - **Business (GTM)** - [Market](/docs/product/business/market): The regulated-knowledge-worker beachhead and how the market is sized. - [Monetization](/docs/product/business/monetization): The pricing model and the liability math that anchors it. - [Legal beachhead](/docs/product/business/beachhead-legal): Why Legal first — BIPA, two-party consent, and privilege. - [Competitive landscape](/docs/product/business/competitive): Where Conclave sits versus notetakers, team-knowledge, and personal-memory tools. - Flows - [User flows](/docs/flows): How the important journeys work, mapped step by step — for people and for developers. - [For people](/docs/flows/for-people): The everyday journeys — record, name a speaker, own your voice, ask, share. - [For developers](/docs/flows/for-developers): The technical flows — the meeting spine, durable jobs, VFTE, permissions, deploy. - Engineering - [Architecture](/docs/engineering/architecture): System topology — the three-repo boundary and the service map. - [Data flow](/docs/engineering/data-flow): How a meeting flows — capture → diarize → identify → enrich → view. - [Repositories](/docs/engineering/repos): Where each piece lives and what it owns. - **Operations** - [Local development](/docs/engineering/local-development): The docker-compose matrix, envctl, and the INTERNAL vs BROWSER URL rule. - [Deployment](/docs/engineering/deployment): Phala TEE CVMs, images, the TLS-passthrough ingress, and the deploy flow. - [Gotchas](/docs/engineering/gotchas): Hard-won deployment gotchas worth reading before you touch prod. - **Status & plan** - [Status](/docs/engineering/status): What is actually built and shipped, with honest badges. - [Roadmap](/docs/engineering/roadmap): Planned, not-yet-built work — derived from the live GitHub issue tracker. - [P0: diarization](/docs/engineering/p0-diarization): The current active workstream — latency and reliability, in four tracks. - **Reference** - [API reference](/docs/engineering/reference/api): The HTTP surface of each service. - [Configuration](/docs/engineering/reference/config): Key environment variables per service. - [Data model](/docs/engineering/reference/data-model): Schema highlights and the load-bearing migrations. - Contributing - [For agents](/docs/contributing/for-agents): How an AI agent should read this repo and where the source of truth lives. - [Build workflow](/docs/contributing/build-workflow): Branch-per-task, git worktrees, test gating, mutation audits, and no push without approval. - [Writing docs](/docs/contributing/doc-style): How to write a page here — dense, cited, no slop.