Release gate: v3.recording-consent-flow.v1
Verifier: pnpm verify:v3 recording-consent-flow
This gate covers V3/V3_TODOS.md §73A. Tara classes, Commons cohorts, and
lectures use per-participant consent. Saraswati concerts use ticket-terms
recording consent with a no-cost privacy-seat path for hall and crowd tiers.
Runtime Policy#
The executable policy lives in
libs/v3/lilith-identity-bridge/src/recording-consent.ts and is covered by
libs/v3/lilith-identity-bridge/src/__tests__/recording-consent.spec.ts.
| Area | Runtime behavior |
|---|---|
| Class room gate | Full, observer, and decline-and-leave outcomes become ledger entries before recording starts |
| Minors in class sessions | Full consent is downgraded to observer until guardian confirmation exists |
| Class opt-out | Mid-session downgrade switches to observer and starts redaction at that timestamp |
| Concert ticket terms | Ticket purchase must affirm recording terms before the ticket is issued |
| Concert privacy seats | Hall and crowd tickets can select privacy at zero cost; minors are auto-locked to privacy |
| Front-256 | Full visibility acknowledgement is mandatory; privacy-conscious buyers receive an alternate tier |
| Audience cam | Sequencer audience-cam cues targeting privacy sections are blocked before publish |
| Crowd-band LL-HLS | Attendees are aggregate-only spectators unless editorial highlights a comment after review |
| Publication gate | Operators verify consent ledgers, privacy-seat ledgers, and redaction before release |
| DSAR and withdrawal | V1 DSAR exports include consent decisions, and withdrawal triggers re-render plus takedown cascade |
Drill Evidence#
Drill outcomes are recorded in V3/privacy/recording-consent-drills.json.
Release evidence is recorded in
V3/privacy/recording-consent-flow-release-gate.json.
The gate also references existing media and privacy coverage:
pnpm verify:v3 tara-recording-flowpnpm verify:v3 saraswati-recording-pipelinepnpm verify:v3 dsar-v1-pipeline