Tracing, provenance & insight

Trace event example

Trace IDs and parent event links correlate stages. Reports expose the effective policy, allowed route reasons, processing boundary evidence and usage. This event shape deliberately omits prompt and response bodies.

json

{
  "event_id": "evt_example",
  "parent_event_id": null,
  "trace_id": "trace_example",
  "request_id": "req_example",
  "policy_ref": "pol_engineering@3",
  "stage": "input",
  "outcome": "allowed",
  "location": "customer_server",
  "region": "eu",
  "region_evidence": "verified",
  "duration_ms": 12,
  "content_retained": false
}

What the workspace should explain

Show the model/provider selected, why candidates were excluded, the applied policy and grammar revisions, stage outcomes, branch status, latency and token/cost reconciliation. Display missing evidence instead of filling gaps with guesses.

Origin and integrity

Record actor/device assurance, permitted transformation lineage and signed or hash-linked events. Use domain-separated keyed digests where content fingerprints are permitted. Provenance can support integrity and origin claims; it does not prove correctness, human authorship or legal ownership.

Reports and retention

Tenant-scoped report APIs export redacted usage, provenance and sovereignty evidence with explicit coverage and uncertainty. Metadata has its own retention policy. Content retention requires separate authorization and never enrolls enterprise data into sale or discount exchange.