Conclave
Your team's confidential memory — every meeting, searchable, and even we can't read it. The reference for humans and agents.
Conclave is your team's confidential memory. Every meeting your team has — captured, searchable, and reasoned over — and built so that even the people who run it can't read your data. Most meeting AI makes you trade intelligence for control. Conclave removes that trade.
The system is three cooperating products behind one boundary:
- Conclave — the intelligence + control plane. The TEE where content lives (transcripts, summaries, insights, knowledge base, audio).
- Capture — meeting capture + acoustic diarization. Joins online meetings or streams a room mic. Identity-free by design.
- VFTE — the voice-identity + consent layer. Turns audio into voiceprints, recognizes speakers scoped and consented.
The load-bearing idea. Access is not privacy. Logins decide who gets in; only encryption + a TEE decide what the vendor can read. Conclave's reads are operator-blind and attested — verify, don't trust.
Start here
For humans
Start with the three-product overview, then the trust model and concepts.
For agents
Read order, conventions, and the source-of-truth map. Also: /llms.txt and /llms-full.txt.
The tiers
Product
What Conclave is, why it exists, the concepts, the feature catalog, and the go-to-market.
Flows
The important journeys mapped step by step — for people and for developers.
Engineering
Architecture, data flow, local dev, deployment, honest build status, and reference.
Agent-friendly by construction
Every page is plain MDX you can read straight from the repo. The site also serves
/llms.txt (an index of every page) and /llms-full.txt
(the entire corpus as one plain-text document), and each page has a Copy as Markdown
button. Point your agent at any of these.
One rule for this repo: we document only what is implemented. Planned work lives on the Roadmap, derived from the live GitHub issue tracker and clearly labelled as not-yet-built. See Status for what actually ships.