Conclave Docs

The three products

Conclave, Capture, and VFTEE — one mental model for the whole system.

Conclave is three cooperating products behind one trust boundary. Get this mental model and the rest of the docs fall into place.

ProductRoleHolds
ConclaveThe intelligence + control plane. The TEE where content lives. Owns UI, auth, workspaces, sharing, jobs.All meeting content + the user ↔ workspace graph
CaptureThe meeting-capture + diarization microservice. Joins online meetings or streams a room mic; does acoustic diarization + ASR. Identity-free.Nothing persistent (stateless; audio by reference)
VFTEEThe voice-identity + consent layer. Turns audio into voiceprints, recognizes speakers scoped + consented, owns the consent plane. Product-agnostic.Voiceprints + consent edges (never audio or content)

The data flow

Meeting
A conversation
in-person · online
Capture
Diarize
who spoke when · anonymously
Conclave
Finalize
persist inside the TEE
VFTEE
Recognize who
scoped + consented
Conclave
Enrich
summary · insights · KB
User
Views · edits · shares
their own space
Throughout, the subject is notified and controls their voice — claim · pause · be forgotten.

In one line: a meeting is diarized anonymously by Capture, finalized by Conclave, named only with consent by VFTEE, enriched back in Conclave, and surfaced to the user — while the subject is notified and keeps control of their voice throughout.

Two graphs, one boundary

The reason this split matters: Conclave owns user ↔ workspace; VFTEE owns voiceprint ↔ scope. They meet at exactly one opaque mapping — settings.fpm_workspace_for(workspace_id) — a scope id that VFTEE attaches no meaning to. That opacity is what keeps VFTEE a general identity layer any app can hook into, and it's why capture emitting {start, end, local_speaker} and nothing else is the load-bearing boundary of the whole system.

Why three products, not one. Separating capture (who spoke) from identity (who that is) from intelligence (what it means) is what lets consent live at the microphone and lets the operator stay blind to content. Collapse them and the privacy story collapses too.

Where to go next

  • Why Conclave — the positioning and what makes it different.
  • Trust model — operator-blindness and attestation.
  • Concepts — voiceprints, consent, workspaces, diarization, the knowledge graph.
  • Features — the shipped catalog for Conclave, verifiable redaction (strip regulated data in-enclave, or bring your own policy, with an offline-verifiable receipt), Capture, VFTEE.

On this page