Repository navigation
evidence(OMN-15769): OCC Evidence-Source autobind for OmniNode-ai/omninode_infra#831 - #6235
Merged
jonahgabriel merged 4 commits intoAug 8, 2026
Merged
Conversation
…fra#831 OCC companion by node_pr_lifecycle_fix_effect (OMN-13317 F1 / OMN-13990 / OMN-14285). Product PR head 4b103cc358600941a843f9b60da5813c06c8cb28.
…ode_infra-pr-831-occ-autobind # Conflicts: # contracts/OMN-15769.yaml # drift/dod_receipts/OMN-15769/dod-occ-evidence-admissibility-validator/command.yaml
…lution The earlier merge-conflict resolution rewrote the shared "dod-occ-evidence-admissibility-validator" dod_evidence entry and its receipt file, both of which were already merged to dev by OCC#6234 (PR #830's companion). That trips the OCC Append-Only Gate: a merged dod_evidence entry/receipt must never be edited, only superseded via a net-new record. Per the established pattern for this exact shape (OMN-15637, PR #795 landing after PR #794's companion already merged the same shared validator-item id): leave the merged "dod-occ-evidence-admissibility- validator" entry and its receipt untouched, and add PR #831's evidence as net-new dod_evidence items (dod-OmniNode-ai-omninode_infra-pr-831, -831-ci, occ-self-bind-pr-6235) instead of duplicating the shared id. Zero merged content edited or deleted; three net-new entries appended.
jonahgabriel
deleted the
auto/omninode-ai-omninode_infra-pr-831-occ-autobind
branch
August 8, 2026 23:49
jonahgabriel
added a commit
that referenced
this pull request
Aug 9, 2026
Append-only conflict: dev merged occ-observation-run31264610218-1 (PR #2026) while this PR carried occ-observation-run31055159329-1 (PR #2022) + occ-self-bind-pr-6134. No id collisions. Keep dev's entry byte-intact first, append this PR's two entries net-new after, per the OMN-15637/#6235 append-only precedent.
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.
Autobind OCC evidence for
OMN-15769.Triggered by node_pr_lifecycle_fix_effect OCC companion emitter on OmniNode-ai/omninode_infra#831 (OMN-13317 F1 / OMN-14285).
Evidence-Ticket: OMN-15769