chore(rivet): close RQ-64-DEPS and record WHY RQ-64-ARCHMODEL defers - #1192
Merged
Conversation
…rred — a scope decision, surfaced rather than silent Two artifact updates, no code. RQ-64-DEPS -> implemented. Both done-when clauses are discharged: the MINORHOLD exit condition landed in #1186, and all four held bumps now have a disposition recorded on the PR itself — #1106 and #1110 and #1107 merged for three different reasons, #1108 closed as genuinely breaking. Four bumps, four outcomes, each on its own evidence. The z3 decline is the FIRST time the enforced hold has stopped a breaking 0.x-minor before it landed; the rule was written after ordeal 0.9->0.12 hung CI for days (#849) and had never been falsified until now. RQ-64-ARCHMODEL stays `proposed` with its reason attached, following the v0.63 precedent (3540292). spar#445 is still OPEN with no activity since 2026-09-03, re-verified at cut time rather than carried forward. It is an EXTERNAL blocker, categorically different from a deferral for scope: nothing here went stale and nothing got harder — it cannot proceed because the tool it depends on silently ACCEPTS input it should refuse. Fourth consecutive release recording feature-loop steps 1-2 as N/A, tracked by #1136. Noted in the artifact: the conformance gate does not accept that prose as evidence — it derives NA-FILED only from a release-SCOPED artifact existing, so the obligation is discharged by filing, not by asserting "synth is a Rust compiler, not AADL-architected". That assertion is true and has never been examined, which is the point of #1136. Verified: rivet at main's 40-error cross-repo baseline with 0 broken cross-refs, status_evidence exit 0, claim_check 62/62. Refs #965, #1136 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YJK5LZZEkV5smCY1jKn18L
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
v0.64 release prep — two artifact dispositions, no code
RQ-64-DEPS→implementedBoth
done-whenclauses discharged. The exit condition landed in #1186; all fourheld bumps now carry a disposition on the PR itself:
Bazel Build & Proofs; green on main and on 3 siblings sharing the baseKanired wasInstall Kani— environmental, still blocked, cleared on re-runFour bumps, four outcomes, each on its own evidence. That spread is the argument
for the exit condition being a procedure rather than a policy: "0.x-minor is
breaking, so hold" produces the queue; only per-bump evidence says which way each
one goes.
#1108 is the first time the enforced hold has stopped a breaking 0.x-minor
before it landed. The rule was written after ordeal 0.9→0.12 auto-merged as a
"minor" and hung CI for days (#849), and had never been falsified until now.
RQ-64-ARCHMODELstaysproposed, with its reason attachedFollowing the v0.63 precedent (
35402926). spar#445 is still open, noactivity since 2026-09-03 — re-verified at cut time, not carried forward.
This is an external blocker, categorically different from a scope deferral:
nothing went stale, nothing got harder. It cannot proceed because the tool it
depends on silently accepts input it should refuse, and building an
architecture model on a parser that won't tell you when you got it wrong produces
exactly the unfalsifiable artifact this programme exists to avoid.
Fourth consecutive release recording feature-loop steps 1-2 as N/A (#1136). The
artifact notes something easy to miss: the conformance gate does not accept
that prose as evidence. It derives
NA-FILEDonly from a release-scopedartifact existing — so the N/A is discharged by filing, not by asserting "synth
is a Rust compiler, not AADL-architected". That assertion is true, and has never
been examined, which is the point of #1136.
Verified: rivet at main's 40-error baseline with 0 broken cross-refs,
status_evidenceexit 0,claim_check62/62.Refs #965, #1136