Repository navigation
evidence(OMN-16115): OCC companion for OmniNode-ai/omnibase_infra#2766 - #6612
Merged
Merged
Conversation
…base_infra#2766 The occ-autobind born-path event was swallowed at the consumer for this PR. The original PR-open trigger (job 95292560731, run 31997821498, 05:26:34Z) published event_id 92e8286a-2ecf-43fa-9bd4-6605dee28bd3 -- but BEFORE the PR was retitled to carry the OMN-16115 ticket token, so that event never named a ticket at all. One authorized workflow_dispatch replay after the retitle (event_id 871d0f42-f3e0-4437-87c6-4153f5ca89f4, 12:54:48Z, confirmed published to onex.cmd.omnimarket.occ-autobind.v1 on the dev-lane broker) produced no companion after 30+ minutes. Hand-authored per controller authorization, on the OMN-16112/occ#6589 and OMN-16114/occ#6595 manual-companion precedent. Two content-bound, admissible-from-the-start probes (learned from the OMN-16112/occ#6589 lane's Contract Compliance Check BLOCK on bare `gh pr view` evidence): dod-OmniNode-ai-omnibase_infra-pr-2766 confirms `async def run_worker_loop(` landed in scripts/edge_delegation_worker/worker_cycle.py at #2766's head (ebd4c098fef2eea1fa9f2df6217429436e627192), RED-verified against the PR's base ref (a5945502fa170805c2fce9247c8be58eac657374, where the file 404s entirely). dod-OmniNode-ai-omnibase_infra-pr-2766-ci confirms the PR's actual diff file list via pulls/2766/files, RED-verified against a fabricated file list. Both SIGPIPE-safe per OMN-15411 Rule E (producer output buffered into a shell variable before the grep -q consumer reads it, occ#5496/#5523 repair idiom) and both re-executed directly (exit 0) against the final staged receipt bytes. contract_sha256/ contract_entry_sha256 computed via the canonical omnibase_core.validation.validator_receipt_gate hashers.
|
Caution Review failedAn error occurred during the review process. Please try again later. Comment |
OCC companion PR #6612 -- self-bind for OMN-16115, mirroring the occ-self-bind-pr-6595 shape. validator_occ_merge_eligibility requires at least one PASS receipt on the cited ticket to bind to the OCC PR carrying the evidence, otherwise the companion is ineligible with reason pr_ticket_mismatch. contract_sha256 recomputed for all three receipts against the contract bytes with the self-bind entry added; contract_entry_sha256 for the two pre-existing items is unchanged (per-entry hash is position-independent, OMN-13888).
jonahgabriel
enabled auto-merge (squash)
August 17, 2026 14:00
jonahgabriel
added
the
ci:ready
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.
What
Hand-authored OCC Evidence-Source companion for OmniNode-ai/omnibase_infra#2766
(edge-delegation-worker outbound-only claim/infer/publish/ack worker).
Why hand-authored
The occ-autobind born-path event was swallowed at the consumer for this PR. The original
PR-open trigger (job 95292560731, run 31997821498, 05:26:34Z) published
event_id=92e8286a-2ecf-43fa-9bd4-6605dee28bd3— but before the PR was retitled tocarry the
OMN-16115ticket token, so that event never named a ticket at all. Oneauthorized
workflow_dispatchreplay after the retitle(
event_id=871d0f42-f3e0-4437-87c6-4153f5ca89f4, 12:54:48Z, confirmed published toonex.cmd.omnimarket.occ-autobind.v1on the dev-lane broker) produced no companion after30+ minutes. Authored per controller authorization, on the OMN-16112/occ#6589 and
OMN-16114/occ#6595 manual-companion precedent.
Evidence
Two content-bound, admissible-from-the-start probes:
dod-OmniNode-ai-omnibase_infra-pr-2766: confirmsasync def run_worker_loop(landedin
scripts/edge_delegation_worker/worker_cycle.pyat evidence(OMN-13226): publisher self-hosted-reroute follow-up receipt #2766's head(
ebd4c098fef2eea1fa9f2df6217429436e627192), RED-verified against the PR's base ref(the file 404s entirely there).
dod-OmniNode-ai-omnibase_infra-pr-2766-ci: confirms the PR's actual diff file list viapulls/2766/files, RED-verified against a fabricated file list.Both SIGPIPE-safe per OMN-15411 Rule E (producer output buffered into a shell variable
before the
grep -qconsumer reads it).Evidence-Ticket: OMN-16115