# V6-002 — Live operational evidence boundary

Date: 2026-07-27

The remaining V6-002 product box concerns external deployment and provider
traffic. `scripts/v6/verify-live-operational-evidence.mjs` now requires one
fresh, source-commit-bound exercise proving:

- a deployed WebTransport handshake and selective SFU forwarding with measured
  end-to-end latency at or below 750 ms and an immutable session artifact;
- live, non-test vendor ASR and TTS requests with model and provider receipts,
  immutable transcript/audio, active subject-specific voice consent, and an
  exercised failover receipt;
- production V6-to-V1 publication with signed publisher receipt, immutable
  content, and verified target readback;
- OTLP collector export with trace ID, nonzero spans, export receipt, backend
  query visibility, and an immutable trace artifact; and
- live Themis case delivery, human acknowledgement, accepted/remediated/
  escalated disposition, and immutable case/receipt evidence.

Provider IDs marked fake, fixture, mock, stub, synthetic, or test are rejected.
Static endpoint configuration, local in-memory transport tests, provider names,
or queued-but-unacknowledged dispatches cannot pass.

The retained evidence and readiness files are
`evidence/v1-v9/V6-002-live-operational-evidence.json` and
`evidence/v1-v9/V6-002-live-operational-readiness.json`. All five checks remain
blocked because no coherent deployed exercise exists.

Verification:

- `node --test scripts/v6/verify-live-operational-evidence.test.mjs`
- `node --check scripts/v6/verify-live-operational-evidence.mjs`
- strict CLI rejects the retained empty package
- `--report` reproduces the retained readiness JSON

The remaining V6-002 checkbox stays open. This gate admits future production
facts without fabricating them from repository-local resilience tests.
