VFTEE as a service

VFTEE is built as the identity + consent layer for Conclave, but it was deliberately kept product-agnostic so it can be rented as infrastructure. The pitch: a voice you own.

For the person

Enroll your voice once, own it, and be recognized only in workspaces you agreed to, with a real consent plane:

• Claim your voice (bind it to your email).
• Pause enrollment or stay anonymous per scope.
• Be forgotten — hard delete with a signed, offline-verifiable receipt.
• See a full usage ledger — every recognition recorded and notified.

A participant can say "don't record me" or "redact my name" and it's honored automatically, because consent lives at the microphone.

For the app

Any product hooks in by passing its own scope + host + consumer token. VFTEE attaches no meaning to the scope id, so there's no client-specific code:

• Opaque workspace_id, pluggable consumer string in the ledger.
• Generic, fail-closed M2M scopes (enroll | identify | voiceprints | …) — not product names.
• One-way knowledge channel, neutral branding.

Think of it as identity + consent for voice the way Stripe is for payments or Auth0 is for login. Conclave and Capture are tenant #1 and #2.

Status

The identity engine, consent plane, deletion proofs, and export/import are built and merged on VFTEE main (see VFTEE features and Status). "VFTEE as a metered external product" is a direction — the standalone-API framing is the thesis for where the identity layer is headed, built on the same engine Conclave and Capture already run against.