Evidence is a product surface, not a dump of every prompt and token. The schema should support review while minimizing sensitive data and separating operational telemetry from durable user-facing records.
Schema principles
- Typed, ordered, attributable, and versioned events.
- Hashes or references when full content is unnecessary or prohibited.
- Explicit uncertainty and missing evidence.
Evidence event shape
{
"eventId": "evt_01J...",
"runId": "run_01J...",
"sequence": 42,
"occurredAt": "2026-06-20T09:41:30.881Z",
"type": "tool.completed",
"actor": { "type": "runtime", "id": "runtime_repo_update" },
"subject": { "toolId": "repository.applyPatch", "version": "1.0" },
"policyDecisionId": "decision_01J...",
"data": { "artifactRefs": ["artifact_patch_01J..."] },
"classification": "internal",
"integrity": { "contentHash": "sha256:..." }
}Required event types
| Event | Purpose |
|---|---|
| run.created | Requester, objective, risk, contract versions |
| context.selected | Sources, provenance, scope, exclusions |
| policy.decided | Rule, subject, action, result, rationale |
| approval.requested / resolved | Human decision and conditions |
| tool.started / completed / failed | Validated action, result, side effect |
| checkpoint.created | Recoverable state boundary |
| artifact.produced | File, diff, report, or external reference |
| run.completed / failed / terminated | Terminal state and remaining uncertainty |
Privacy and retention
Store the minimum content required for the stated review purpose. Separate secrets from evidence, classify sensitive fields, enforce tenant boundaries, support deletion and legal holds, and record access to evidence itself. OpenTelemetry conventions can improve interoperability, but retention and user-facing semantics remain product decisions. Source: OpenTelemetry
Download the evidence schemas
The evidence-event and policy-decision schemas provide a portable starting point for attributable runtime records and reviewable governance decisions.
Status: MiRuntime editorial reference artifacts. These files are not an SDK, certification, or industry standard.
Conceptual policy decision
JSON Schema for allow, deny, approval, transformation, and escalation decisions evaluated during execution.
Conceptual evidence event
JSON Schema for ordered runtime events, actors, status, tools, approvals, artifacts, errors, uncertainty, and integrity metadata.
Source record
References
OpenTelemetry project. Cloud Native Computing Foundation. Published Current specification repository; last reviewed 2026-06-24 UTC. Official specification.
National Institute of Standards and Technology. NIST. Published 2024-07-26; last reviewed 2026-06-20 UTC. Government profile.