Skip to content

evidence(OMN-16071): OCC companion for OmniNode-ai/omnimarket#2086 - #6606

Merged
jonahgabriel merged 3 commits into
devfrom
auto/omninode-ai-omnimarket-pr-2086-occ-autobind
Aug 17, 2026
Merged

jonahgabriel merged 3 commits into
devfrom
auto/omninode-ai-omnimarket-pr-2086-occ-autobind

Conversation

@onexbot-occ-writer

Copy link
Copy Markdown
Contributor

Deterministic OCC evidence companion for OmniNode-ai/omnimarket#2086, 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).

@onexbot-occ-writer
onexbot-occ-writer Bot force-pushed the auto/omninode-ai-omnimarket-pr-2086-occ-autobind branch from 8891a49 to b1e0baa Compare August 17, 2026 12:37
@onexbot-occ-writer onexbot-occ-writer Bot added ci:ready Full CI runs on this PR (OMN-15731 label-gated CI pilot) occ:machine-minted labels Aug 17, 2026
node_occ_companion_effect's own pass-2 (self-bind + Evidence-Source stamp)
never reached this ticket: its automated retry aborted with an
append-only violation on contracts/OMN-16071.yaml -- omnimarket #2086's
own hardened _assert_append_only guard correctly refusing a stale-based
re-render, caused by heavy same-day concurrent OCC contract activity on
this exact ticket (occ#6550, occ#6590 both landed today). That guard did
its job: nothing corrupt was pushed. Hand-authoring the missing self-bind
entry + receipt here, mirroring the occ-self-bind-pr-6550/-6590 precedent
on this same contract exactly, so occ-preflight/eligibility and
verify/verify on OCC#6606 do not fail closed with pr_ticket_mismatch.

Pure append relative to the current dev tip (verified byte-identical to
this branch's own pass-1 commit before appending -- not a repeat of the
race): validator_occ_append_only.evaluate_append_only -> ok=True, zero
violations. validate_occ_merge_eligibility -> eligible=True. yamlfmt
-lint clean (hashes computed against the yamlfmt-stable bytes). Local
pre-commit on both changed files: 0 failures.

Evidence-Ticket: OMN-16071
@jonahgabriel
jonahgabriel enabled auto-merge (squash) August 17, 2026 12:53
…a256

The automated node_occ_companion_compute pass-1 minted
drift/dod_receipts/OMN-16071/dod-OmniNode-ai-omnimarket-pr-2086/command.yaml
with a legacy contract_sha256-only binding (no contract_entry_sha256,
and evidence_item_id "dod-OmniNode-ai-omnimarket-pr-2086" is not itself
declared as a dod_evidence item in contracts/OMN-16071.yaml -- a
pre-existing gap in the compute plan's "second product PR on an
already-companioned ticket" handling, unrelated to this fix). A
legacy-only binding goes stale on every later contract append regardless
of which entry changed (docs/standards/receipt_hashing_and_supersession.md
section 2) -- and the prior commit on this branch (occ-self-bind-pr-6606)
appended a new entry, staling this receipt's whole-file hash. Rebinding it
to the current contract hash is a pure edit of a file this same open,
unmerged PR (OCC#6606) already introduced -- it does not exist on dev, so
it is still a net "A" relative to the merge base regardless of how many
times it is edited before merge; not a mutate-in-place violation.

scripts/validation/check_receipt_hardening.py run locally against every
receipt in this PR's diff: 0 violations (was 1). validate_occ_merge_eligibility
-> eligible=True. validator_occ_append_only.evaluate_append_only -> ok=True.

Evidence-Ticket: OMN-16071
@jonahgabriel
jonahgabriel merged commit d8d988f into dev Aug 17, 2026
298 of 314 checks passed
@jonahgabriel
jonahgabriel deleted the auto/omninode-ai-omnimarket-pr-2086-occ-autobind branch August 17, 2026 17:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci:ready Full CI runs on this PR (OMN-15731 label-gated CI pilot) occ:machine-minted

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant