Select a mapping to inspect its field paths and evidence boundary.
Evidence IR · Versioned crosswalk
Trace the evidence path.
See how native inputs map into common evidence, and how that evidence reaches an output. Inspect the fields, implementation and limits behind each connection.
A mapped path is not a guarantee for every artifact. Optional layers require additional inputs. Native facts, derived values, declarations and imported observations retain their evidence boundaries.
Mapping explorer
Loading mappings…
No matching mappings. Clear a filter or try another field name.
How to read mapping status
- Implemented
- A concrete implementation path exists; referenced checks do not mean every possible artifact is tested.
- Conditional
- Requires a compatible artifact, decoder, binding or supplied evidence; inspect run coverage.
- Preview
- A bounded adapter exposes only the listed native scope.
- Proposed
- A design boundary is recorded; there is no working adapter.
Field groups are a navigational crosswalk, not a complete leaf-by-leaf conversion specification. Auxiliary command schemas and runtime-specific profile fields are outside this first catalog.
Input schemas
Native binary formats retain their own contracts. JSON evidence inputs link to the applicable schema definition.
Output schemas
Exports have different evidence scopes. A proposed exchange route is listed separately from implemented document exports.
A shared, inspectable baseline
Catalog versions, member schema identities, calculation methods and engine releases are independent. Published snapshots retain their bytes and SHA-256. The same generated snapshot feeds this page and GitHub; links to implementation files show the current repository, while the snapshot records exact source-file digests.
Review and version policy · IR member catalog · IR family schema