Common representation · Draft specification
One evidence family.
Distinct evidence boundaries.
DEEPBOM Evidence IR connects multiple model formats and optional evidence inputs through shared identities, references and validation rules. Each member answers a different question.
Input → common IR → output
Open the compatibility explorer to search versioned field mappings, distinguish implemented and proposed paths, and inspect input/output schemas, source references and evidence limits. The website and GitHub share the same generated catalog.
The five members
| Representation | What it records |
|---|---|
| Artifact IR | Observed artifact structure, native facts and serialized storage. |
| Model IR | A common model program and contracts derived from the validated Artifact IR. |
| Weight IR · optional | Assessed tensor payload statistics, source bindings and explicit coverage limits. |
| Activation IR · optional | Imported execution captures bound to a model, run and probe. Static inspection does not create runtime measurements. |
| Provenance IR · optional | Connections to datasets, code, runs, reports and external BOMs; supplied-file consistency and declared relationships remain distinct. |
Shared rules
Artifact IR is the source for Model IR. Optional members bind to that model without modifying its identity. References, digests, exact counts and coverage must remain consistent. Unknown, unsupported and unassessed values stay explicit.
The family JSON Schema accepts one member document. It is not a bundle format. JSON Schema checks structure; member validators additionally check source bindings and semantic consistency. A digest alone does not authenticate a publisher or prove a lineage claim.
Use and inspect the specification
- Family JSON Schema · Machine-readable member catalog
- Provenance IR schema entry point
- Specification, compatibility checks and maintenance process
- Weight and activation workflows · OMOP metadata connections
These names describe a DEEPBOM-maintained specification. They do not imply endorsement or certification by OMOP, CycloneDX, SPDX or W3C. External mappings retain their source standards and limits.
Current contract and transition
Provenance IR uses deepbom.provenance_ir.v1, provenance_ir_sha256, and the sole --section provenance_ir selector. Retired names are rejected. Regenerate evidence from the model, a current metadata template and supporting files; do not relabel an old hashed document.
The 2.0.0 release introduces this breaking transition across web assets, CLI and remote MCP validators. Read the transition rules.
Exchange through TEA
TEA describes discovery and exchange of transparency documents. It can deliver future exports while Evidence IR continues to define and validate their evidence. A TEA adapter is proposed, not implemented. Read the pinned specification review.