Governance & enterprise
Audit and observability
Explain routing without turning telemetry into a content store
Octoryn exposes content-free operational evidence: request correlation, route decisions, aggregate usage, provider health and policy outcomes. Prompts and outputs are not required to explain why a route was selected or denied.
Correlate each request
Capture the Router request ID, workspace-owned service identity, status, latency and terminal outcome. Keep bearer tokens and detected sensitive values out of logs.
Explain policy decisions
Evidence should identify the policy version, matched constraint, selected or rejected provider class, region and reason code. Use hashes only where they add integrity, not as a substitute for safe data handling.
Use the right surface
Use Console governance for tenant-scoped usage and audit, the public status page for service health, and provider health evidence for operator decisions. Source code existence is not proof that production is serving a capability.