Repository navigation
evidence(OMN-15744): falsifiable deploy-gate probe for omnibase_infra#2686 - #6209
Conversation
The prior dod-deploy-assessment entry (autobind-generated, pre-existing, protected by the append-only invariant) uses gh pr diff --name-only | grep -c, which the deploy-gate falsifiability ratchet correctly rejects as vacuous (no live-surface command in command position). This appends a net-new dod_evidence item that uses the ratchet's own documented "Good (compute-only/no-live-deploy tickets, hermetic under OMN-14051)" pattern: gh api reads docker/docker-compose.gateway.yml from omnibase_infra at PR #2686's head SHA and asserts the b-3 broker FQDN is present in extra_hosts -- a real repo-state check whose exit status depends on the actual diff (0 matches on dev HEAD pre-fix, 4 matches on the PR head post-fix; verified live before writing this contract entry). OMN-15744
…probe Records the live gh api probe output (grep -c returns 4 on PR #2686 head SHA) that backs the deploy-scope-falsifiable-probe dod_evidence entry. Falsifiability against dev HEAD (0 matches pre-fix) is documented in actual_output; probe_stdout carries only the declared command's literal terminal output per the Receipt Hardening Gate's shape-consistency rule. OMN-15744
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 57 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
Comment |
…-RED Contract Corpus Ratchets (OMN-15411, Rule E) correctly flagged the deploy-scope-falsifiable-probe check_value: piping an unbounded gh api producer straight into base64 -d | grep -q lets grep exit at the first match, SIGPIPE-killing the upstream producer, which the dod_verify runner's `bash -o pipefail` turns into a false RED (exit 141) even though the evidence is present. Buffer the producer into a variable first, per the ratchet's own remediation text. OMN-15744
Rebinds contract_sha256/contract_entry_sha256 to the buffered check_value and reruns the probe fresh (grep -cF returns 1, exit 0) rather than reusing the earlier pipefail-fragile output. OMN-15744
The prior fix buffered only the gh api fetch, leaving base64 -d | grep -qF still live-piped -- Contract Corpus Ratchets Rule E flagged that as the same sigpipe-fragile pattern (bucket: base64-decoded file body). Buffer the decoded output into a second variable before the final grep -qF. OMN-15744
…robe fresh OMN-15744
1 participant
Summary
Follow-up to OCC#6204 (merged). The deploy-gate falsifiability ratchet
(OMN-14443/OMN-14505) correctly rejected
OMN-15744.yaml's pre-existingdod-deploy-assessmententry (autobind-generated,gh pr diff --name-only | grep -c— no live-surface command, protected by the append-only invariantso it cannot be edited). This adds a net-new
deploy-scope-falsifiable-probedod_evidence entry using the ratchet's own documented "Good" pattern:
gh apicontent-readsdocker/docker-compose.gateway.ymlfromOmniNode-ai/omnibase_infra at PR #2686's head SHA and asserts the
b-3broker FQDN is present in
extra_hosts.Falsifiability verified live before writing the contract entry: the
identical probe against
devHEAD (pre-fix) returns 0 matches / exit 1;against PR #2686's head SHA it returns 4 matches / exit 0. Receipt:
drift/dod_receipts/OMN-15744/deploy-scope-falsifiable-probe/command.yaml.Ticket
OMN-15744