JSON Schema
Requirements v0.2 JSON Schema
The backward-compatible current schema, adding capture provenance, dropped-record indication, and truncation indication.
Download JSON SchemaOperational artifact
Trace Reconstruction Requirements
A machine-readable way to state what evidence a team needs for a reconstruction use case before evaluating whether a trace provides it.
Direct answer
The requirements file defines the target; it does not grade a vendor.
A profile names a use case and its required evidence, such as initiating principal, stable agent identity, model version, tool arguments and results, authority scope, human approval, external state, timestamps, and integrity evidence. Tracevity Inspect can evaluate a supported local trace against that target without uploading it.
From target to local release policy
Inspect the evidence, then gate changes against the same requirement.
Compatibility bindings describe the exact trace semantics Tracevity has exercised. The Inspector applies those bindings to a supported artifact and reports established, partial, not-established, indeterminate, or external-evidence-required results. Gate compares baseline and candidate results and blocks material required regressions.
Start here
Current schema and capture-completeness example
Use the schema for validation and the incident profile as a complete worked example.
YAML example
Incident capture completeness
A v0.2 incident profile that prevents missing exported evidence from becoming a definitive negative.
Download YAML exampleAll artifacts
Choose a use-case example
| Artifact | Format | Purpose | Download |
|---|---|---|---|
| Requirements v0.2 JSON Schema | JSON Schema | The backward-compatible current schema, adding capture provenance, dropped-record indication, and truncation indication. | Download |
| Incident capture completeness | YAML example | A v0.2 incident profile that prevents missing exported evidence from becoming a definitive negative. | Download |
| Requirements JSON Schema | JSON Schema | The normative machine-readable structure for a v0.1 requirement profile. | Download |
| Trace Evidence Binding v0.1 | JSON Schema | The independently versioned schema for binding concrete trace fields and relationships to reconstruction capabilities. | Download |
| Trace Evidence Binding v0.2 | JSON Schema | The additive exercised-compatibility schema used by the Inspector's exact declared bindings. | Download |
| Binding v0.2 assertion proofs | JSON registry | The current proof registry: 26 preserved historical exact proofs plus one additive corrected forward proof and its explicit supersession trail. | Download |
| Inspection Manifest v0.1 | JSON Schema | Declares the local input artifact, exact dialect, signal kind, and binding. | Download |
| Correlated Evidence Envelope v0.1 | JSON Schema | Defines optional external evidence provenance and strong correlation keys. | Download |
| Reconstruction Report v0.1 | JSON Schema | Defines deterministic per-requirement results, evidence, limits, and digests. | Download |
| Model identity binding | JSON example | A minimal worked binding with documented, interpreted, and Tracevity-tested layers. | Download |
| Incident reconstruction | YAML example | A worked requirement profile for reconstructing a security or reliability incident. | Download |
| Basic debugging | JSON example | The evidence target for diagnosing model, tool, latency, and error behavior. | Download |
| External-effect verification | JSON example | Separates requested action, provider acceptance, and verified destination state. | Download |
| Privacy-controlled archival | YAML example | Expresses retention, redaction, filtering, deletion, and capture-control evidence. | Download |
Use-case specific
No universal score
Requirements are attached to a named reconstruction outcome. A field can be essential for one use case and unnecessary for another.
Evidence aware
Missing and unverifiable stay visible
The framework is designed to preserve partial, missing, ambiguous, and externally unverified states instead of coercing them into pass or fail.
Local-first public beta
No trace upload
Tracevity Inspect evaluates supported traces locally. This website does not accept, analyze, transmit, or retain customer traces.
Read the use-case framework, the Inspector guide, or the Gate guide, or the exercised compatibility evidence alongside the evidence methodology before interpreting a requirement result as an assurance claim.