fix(spec): sync schema + spec doc to v1.6 models, guard against drift - #136
Merged
Conversation
The canonical schema had not been touched since March — none of the v1.6 fields (src_hash, replay, input_hash, metrics, meta.deps) were in it. For a project positioned as an open standard and evaluated as prior art, a reference schema that doesn't describe the format is a real hole. - spec/akf-v1.1.schema.json: add src_hash (Claim), replay + metrics (Evidence), new Replay $def, meta.deps - spec/akf-v1.0-spec.md: document the v1.6 fields - tests/test_schema_conformance.py: stamp a maximal unit, validate against the schema — fails CI if models emit a field the schema doesn't describe (the anti-drift mechanism) - jsonschema added to dev deps; CONTRIBUTING notes the schema-sync rule
AKF Trust Certification — ✅ Certified❌ 0/11 files certified · average trust 0.45 · 3 failed
Total: 11 | Certified: 0 | Failed: 3 | Skipped: 8
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Long-term fix #1 of 2. The canonical schema (
spec/akf-v1.1.schema.json) hadn't been updated since March — none of the v1.6 fields (src_hash,replay,input_hash,metrics,meta.deps) were in it. For a project whose pitch is "an open standard, borrow the fields with or without the dependency" — and which is being evaluated as prior art — a reference schema that doesn't describe the actual format is a credibility hole.src_hash(Claim),replay+metrics(Evidence), a newReplay$def, and documentsmeta.deps. All additive; existing files unaffected (these lived underadditionalProperties: true).akf-v1.0-spec.md.tests/test_schema_conformance.pystamps a maximal unit (every v1.6 field) and validates it against the canonical schema. A field that exists in code but not the schema now fails CI — this can't silently drift again.jsonschemaadded to dev deps; CONTRIBUTING documents the schema-sync rule.Verified: schema is valid Draft 2020-12; real 1.6 stamps validate; full suite 1972 passed.