Repository navigation
evidence(OMN-16323): OCC companion for OmniNode-ai/omnimemory#432 - #6809
Merged
jonahgabriel merged 2 commits intoAug 21, 2026
Merged
Conversation
jonahgabriel
deleted the
auto/omninode-ai-omnimemory-pr-432-occ-autobind
branch
August 21, 2026 04:11
jonahgabriel
added a commit
that referenced
this pull request
Aug 21, 2026
Same gap occ-preflight caught on the sibling companion OCC#6819: reason=pr_ticket_mismatch, because the only receipt on this PR carries pr_number 2827 (the omnibase_infra PR) and nothing bound OMN-16323 to this OCC PR itself. The existing self-binds on this contract cover #6809, #6810 and #6811 -- none of them covers #6820. Adds occ-self-bind-pr-6820 following the convention already used by those three, with the probe run live and the real stdout recorded. Updates the product-PR receipt's contract_sha256, which moved when the file gained an entry; both contract_entry_sha256 values are unchanged, per OMN-13888. Refs: OMN-16323, omnibase_infra#2827, OMN-13888
jonahgabriel
added a commit
that referenced
this pull request
Aug 21, 2026
#6820) * evidence(OMN-16323): OCC companion for OmniNode-ai/omnibase_infra#2827 Rebased onto dev to resolve the add/add on contracts/OMN-16323.yaml that OCC#6811 created when it landed (caa15f5, adding dod-OmniNode-ai-omnimarket-pr-2118 and occ-self-bind-pr-6811). Resolved cumulatively, as flagged in the original PR body: reset to dev so all seven landed entries are byte-identical and in their landed order, then re-appended this entry as the eighth. Verified the landed prefix matches dev byte-for-byte rather than trusting the merge. Only contract_sha256 changed (whole-file hash, necessarily). The contract_entry_sha256 is UNCHANGED at sha256:38b9255119... -- which is OMN-13888 working as designed: the per-entry hash binds to the canonical JSON of its own dod_evidence item plus a pinned header subset, not the whole file, so appending after other entries leaves earlier entries' hashes untouched and leaves this one's untouched when others append before it. Probe unchanged and re-run live after the rebase: exit 0. Refs: OMN-16323, omnibase_infra#2827, OMN-13888 (per-entry hash), onex_change_control#6811 (the entries this rebases over) * evidence(OMN-16323): add the OCC self-bind entry for PR #6820 Same gap occ-preflight caught on the sibling companion OCC#6819: reason=pr_ticket_mismatch, because the only receipt on this PR carries pr_number 2827 (the omnibase_infra PR) and nothing bound OMN-16323 to this OCC PR itself. The existing self-binds on this contract cover #6809, #6810 and #6811 -- none of them covers #6820. Adds occ-self-bind-pr-6820 following the convention already used by those three, with the probe run live and the real stdout recorded. Updates the product-PR receipt's contract_sha256, which moved when the file gained an entry; both contract_entry_sha256 values are unchanged, per OMN-13888. Refs: OMN-16323, omnibase_infra#2827, OMN-13888
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.
Deterministic OCC evidence companion for OmniNode-ai/omnimemory#432, authored by node_occ_companion_effect (RSD-3, OMN-14622) from the node_occ_companion_compute plan. Every byte is a pure function of the compute plan (attestation-oracle reproducible).