registry: mirror covers declarations (spec 1.1.1) and enforce them in the gate - #7
Merged
Merged
Conversation
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_ebc5ccbf-c4c5-4cb4-97a2-ef12d2f1c54a) |
… the gate Mirrors rvt-rs #234: SPEC.md 1.1.1 (refreshed section 6 worked examples, section 5.3.1 coverage row now implemented), registry with `covers` on every adopted reader (authors deliberately excluded), and the registry schema's allOf/if/then conditionals — jsonschema_mini gains allOf, if/then/else and not, keeping the fail-loudly contract. check-registry.py enforces the three rules: adopted readers must declare covers, authors must not, and every committed observation's semantic_surface_covered must be a subset of its witness's declaration. Negative checks exercised for all three.
DrunkOnJava
force-pushed
the
registry/covers-and-spec-1.1.1
branch
from
August 30, 2026 20:25
f0f2a3b to
c77a322
Compare
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
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.
Mirrors rvt-rs #234: SPEC.md 1.1.1 (refreshed §6 worked examples, §5.3.1
coverage row now implemented), registry with on every adopted
reader (authors deliberately excluded), and the registry schema's
allOf/if/then conditionals — jsonschema_mini gains allOf, if/then/else
and not, keeping the fail-loudly contract. check-registry.py enforces
the three rules: adopted readers must declare covers, authors must not,
and every committed observation's semantic_surface_covered must be a
subset of its witness's declaration. Negative checks exercised for all
three.
Note
Low Risk
Documentation and registry validation only; no changes to diff logic, schemas for observations/verdicts, or CI witness execution.
Overview
Bumps OctetProof to 1.1.1 as a non-semantic patch: protocol behavior is unchanged, but the spec and umbrella registry now match what the reference gate already enforces.
Registry coverage (
covers). Adopted readers must declare §9.4 semantic-surface classes inregistry/witnesses.json; authors must not. The witness registry schema addscoversplusallOf/if/then/notrules, andjsonschema_minigrows support for those keywords so validation stays stdlib-only.check-registry.pyenforces the three invariants: adopted readers havecovers, authors lack it, and each corpus observation’ssemantic_surface_coveredis a subset of its witness’scovers.SPEC.md. §5.3.1 and §9.4 document coverage as implemented (not umbrella scope). §6.2/§6.3 worked examples are regenerated from
magnetar-2024-core-interior-slim(three witnesses,relations/storeys, thirteen-field verdict). Section 20a records the release; closes rvt-rs #224 and #229.Reviewed by Cursor Bugbot for commit f0f2a3b. Configure here.