Evidence before a compatibility claim
Reference validation is the first step
Core 0.1.0-draft.1 includes schemas, two synthetic cases, a reference validator, and executable tests. They exercise a candidate binding. They are not a certification program or proof of independent interoperability.
Read the exact validation coverage and limitations before describing an implementation as compatible.
Run the reference checks
From the codex/core-investigation-contract review branch with Node.js 22 or later and dependencies installed:
npm run check:schemas
npm run validate:examples
npm testFull setup instructions · Validate a bundle in the Lab
What the checks can establish
- Structural validity against the candidate binding and schemas.
- Definition pins, reference closure, question context, and explicit transition selections.
- Revision lineage, original inputs, and required review representation.
- Declared handling of partial exchange and unsupported required semantics.
They do not establish evidence truth, legal authority, investigative completeness, security effectiveness, or the safety of an implementation. The validator does not execute recorded actions or fetch evidence locators.
Roles replace a universal badge
| Proposed role | Claim to substantiate |
|---|---|
| Definition producer | Produces pinned, interpretable definitions with explicit question and transition meaning. |
| Record producer | Produces records with valid context, attribution, references, and revision behavior. |
| Reader | Interprets supported content and exposes missing or unsupported meaning. |
| Lossless exchanger | Preserves meaning, required original bytes, and unsupported optional content as opaque data through exchange. |
| Transition interpreter | Resolves explicitly selected assessments and guarded transitions without inventing a default. |
Report a result others can reproduce
Record the specification and binding versions, implementation version, role, profile, test suite and artifact digests, test date, named checks, outcomes, and known exclusions. Distinguish pass, fail, indeterminate, and notRun. An unknown investigative answer can be valid data.
The founding package supplies twelve acceptance scenarios. They describe desired evidence and are broader than a single reference implementation. A self round trip is not an exchange between independent implementations.
Earlier fixtures
The previous website's graph-only starter fixtures belong to the legacy model. Use the candidate release page for new work; do not combine the two contracts under one conformance claim.