Conformance Suite Overview
Conformance prevents compatibility claims from becoming subjective. Use the shared fixtures as a baseline and extend for domain-specific behavior.
Core Suite Artifacts
-
Suite manifest:
conformance/manifest.json -
Valid fixture:
core-minimal.json -
Invalid fixture:
edge-id-mismatch.json -
Compatibility policy:
compatibility-policy.md
Execution Checklist
- Load fixture and schema versions from pinned release channels.
- Run validation in CI and persist the result as machine-readable output.
- Include failing fixture cases to verify rejection behavior.
- Publish conformance tier and tested versions in release notes.
Pass Criteria by Tier
| Tier | Pass Requirements |
|---|---|
| Consumer | Schema-valid input accepted; invalid IDs rejected with explicit message. |
| Executor | Branch traversal aligns with encoded decisions and replayed output is stable. |
| Authoring Tool | Produced artifacts remain schema-valid and preserve ID continuity. |
Reporting Format (Recommended)
- Tested graph version
- Tested schema version
- Fixture pass/fail summary
- Known limitations and unsupported optional fields
Implement next: Implementation guide · Standards policy · Contribute fixture improvements