Telemetry sink
structured-console
Fallback posture; durable endpoint not configured
EVIDENCE + OBSERVABILITY
Durable operational contracts without content leakage
Telemetry exports runtime/governance metadata only. Governed evidence stores integrity-protected object references with SHA-256 metadata and server-mediated access.
Protocol
structured console
Metadata-only export; AI prompts and evidence content are excluded
Evidence store
memory
Memory fallback for interview reliability
Integrity
SHA-256
Non-overwrite object key + hash verification on governed read
Upload → hash → classify → store → attach → verify
The server validates the caller, checks optimistic concurrency, calculates SHA-256, creates a non-user-controlled object key, stores the object, and only then attaches its integrity-protected metadata to the use-case evidence package. If workflow persistence fails, object cleanup is attempted. Downloads are authorized against the tenant-scoped workflow snapshot and hash-verified before release.
Server mediatedSHA-256Non-overwrite keysClassificationNo SAS returned
AI + governance events through one sink boundary
AI runtime events include provider/model/prompt version/latency/tokens/outcome. Workflow events include action, effective role, repository mode and versions before/after. Tenant scope is hashed and business content is intentionally excluded. OTLP export is fail-open so telemetry failure cannot break the interview or commit path.