Repository navigation
evidence(OMN-18796): hand-authored OCC evidence for omnibase_core#1709 - #10521
Merged
Merged
Conversation
Onex-Lane: omn18777-advisory-gate-fanout-five-repos-0208 Onex-Session: 65a60b368023401d8f2f115ce3153841
…ile contract hash Onex-Lane: omn18777-advisory-gate-fanout-five-repos-0208 Onex-Session: 65a60b368023401d8f2f115ce3153841
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.
What
Hand-authored OCC evidence for OmniNode-ai/omnibase_core#1709 on OMN-18796, epic OMN-18775. Authored on the OMN-15247 path because occ-autobind declined the product PR's one-line diff.
Appends three entries to the existing
contracts/OMN-18796.yaml. It does not create the contract:devalready carries it as a structural union over #1708, #3808, #2261 and omninode_infra#1571, and this extends that union rather than colliding with it.The behavior proof is content-bound and falsifiable, measured both directions before authoring
The product change re-pins the advisory-job-gate caller to the omniclaude commit where the reusable installs its own dependency. The probe reads that file's content at a pinned ref and counts the new pin.
Both were run before the receipt was written, not asserted after it. At the merge base the file still names the superseded pin, so the probe separates this change from its own base instead of merely asserting the pull request exists, which OMN-15247 refuses as non-falsifiable.
Hashes come from the canonical functions
Every
contract_entry_sha256is minted bycompute_contract_entry_sha256fromomnibase_core.validation.validator_receipt_gate, imported rather than reimplemented, andcontract_sha256bycompute_contract_sha256from the same module.The append is non-destructive, verified rather than assumed: all ten pre-existing entries hash identically before and after this change, with a positive control confirming the comparison discriminates, since a deliberately mutated entry does drift. The local run of the per-entry rebind re-verification gate passed.
Ticket: OMN-18796