Skip to content

docs(OMN-12738): add qwen delegation evidence - #2222

Merged
jonahgabriel merged 3 commits into
devfrom
jonah/omn-12738-occ-evidence
Jun 6, 2026
Merged

jonahgabriel merged 3 commits into
devfrom
jonah/omn-12738-occ-evidence

Conversation

@jonahgabriel

Copy link
Copy Markdown
Contributor

Summary

  • Add central OMN-12738 OCC contract for Qwen delegation reasoning suppression.
  • Add PASS receipts for omnimarket PR evidence(OMN-11003): bind model collision burndown #1065, focused delegation tests, and deploy-gate assessment.
  • Preserve the no-live-deploy boundary; runtime validation is documented as a post-merge docker exec proof surface.

Verification

  • uv run validate-yaml contracts/OMN-12738.yaml
  • uv run python scripts/lint_contract_check_values.py contracts/OMN-12738.yaml
  • CONTRACT_REPO_DIR=$PWD uv run python scripts/ci/run_contract_compliance_check.py --pr 1065 --repo OmniNode-ai/omnimarket --contracts-dir contracts
  • git diff --check

Ticket: OMN-12738

@coderabbitai

coderabbitai Bot commented Jun 6, 2026 •

Copy link
Copy Markdown

Warning

Review limit reached

@jonahgabriel, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 3 minutes and 5 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 65a33704-f8c3-4d24-a980-6bb7e0389915

📥 Commits

Reviewing files that changed from the base of the PR and between 549217d and ccf60e0.

📒 Files selected for processing (5)
  • contracts/OMN-12738.yaml
  • drift/dod_receipts/OMN-12738/dod-deploy-gate-assessment/command.yaml
  • drift/dod_receipts/OMN-12738/dod-focused-delegation-tests/command.yaml
  • drift/dod_receipts/OMN-12738/dod-occ-pr-2222-evidence/command.yaml
  • drift/dod_receipts/OMN-12738/dod-omnimarket-pr-1065/command.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch jonah/omn-12738-occ-evidence

Comment @coderabbitai help to get the list of available commands and usage tips.

@jonahgabriel
jonahgabriel added this pull request to the merge queue Jun 6, 2026
Merged via the queue into dev with commit 073526b Jun 6, 2026
35 checks passed
@jonahgabriel
jonahgabriel deleted the jonah/omn-12738-occ-evidence branch June 6, 2026 11:46
jonahgabriel added a commit that referenced this pull request Aug 30, 2026
… on one ticket

omnimarket#2222 and omnibase_infra#3035 both carry OMN-17182, so autobind minted
two independent companions that each created contracts/OMN-17182.yaml and
drift/dod_receipts/OMN-17182/dod-occ-evidence-admissibility-validator/command.yaml.
OCC#7703 (omnimarket) merged first, so this branch went add/add CONFLICTING.

Resolved as the UNION of both evidence sets - no entry from either side dropped:

  - dod-OmniNode-ai-omnimarket-pr-2222        (from dev, via OCC#7703)
  - dod-deploy-assessment                     (from dev, via OCC#7703)
  - dod-occ-evidence-admissibility-validator  (from dev, via OCC#7703)
  - occ-self-bind-pr-7703                     (from dev, via OCC#7703)
  - dod-OmniNode-ai-omnibase_infra-pr-3035    (this branch)
  - occ-self-bind-pr-7702                     (this branch)

The single admissibility-validator entry is kept once and left superseding the
omnimarket item, matching the existing multi-PR precedent in contracts/OMN-17155
where later PRs append their own dod + self-bind entries without minting a second
validator. Its receipt is dev's (PR #2222 probe), not this branch's duplicate.

Hashes are RECOMPUTED, not copied. yamlfmt reflowed the merged contract, which
moves the whole-file hash, so contract_sha256 was recomputed for all six receipts
from the formatted bytes via compute_contract_sha256, and contract_entry_sha256
via compute_contract_entry_sha256 against the merged contract_data. Verified with
the repo's own gate: scripts/validation/check_receipt_hardening.py exits 0.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant