plan(rivet): start the release roadmap — v0.1.0 = semaphore (depth-first)#49
Open
avrabe wants to merge 2 commits into
Open
plan(rivet): start the release roadmap — v0.1.0 = semaphore (depth-first)#49avrabe wants to merge 2 commits into
avrabe wants to merge 2 commits into
Conversation
…11 sem requirements - gale had NO release plan in rivet (0 of 924 artifacts scoped). Start the rivet-driven roadmap per release-planning: v0.1.0 = the semaphore primitive, taken end-to-end to verified before the next primitive. - Scope mechanism: 'release-v0.1.0' TAG on the 11 sem requirements (SWREQ-SEM-P01..P10 + SYSREQ-SEM-001). rivet 0.15.0 sw-req/system-req schemas have no native release: field, so tags are the queryable mechanism (filed as rivet friction). - docs/release-plan.md: the readiness burn-down query + cuttability criterion + cadence. - Readiness now: 0/11 verified (all approved) -> NOT cuttable. Burn-down = wire the 16 existing sem verifications (UV/IV/SV/FV-SEM-*) to the reqs, then approved->verified (a traceability-audit pass; part of the 311 lifecycle gaps). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
… ...) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
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
gale had no release plan in rivet — 0 of 924 artifacts carried any release scope, so the V-model trace couldn't drive or gate a roadmap. This starts it, depth-first per the release-planning model.
v0.1.0 = the semaphore primitive, taken end-to-end to
verifiedbefore the next primitive begins.release-v0.1.0tag on the 11 sem requirements (SWREQ-SEM-P01..P10+SYSREQ-SEM-001). rivet 0.15.0'ssw-req/system-reqschemas have no nativerelease:field (the field is tolerated but not queryable by--filter), so tags are the working, queryable mechanism — filed as friction on pulseengine/rivet.docs/release-plan.md: the readiness burn-down one-liner (rivet list --filter '(has-tag "release-vX")' … count), the cuttability criterion, and the per-primitive cadence.Readiness (the query, not an opinion)
All 11 reqs are
approved, noneverified. The gap is linkage, not missing work: 16 sem verifications already exist (UV-SEM-001..005,IV-SEM-001/002,SV-SEM-001,FV-SEM/WQ/PRI/THR/ERR-*, plus the 907-cyc silicon result) but aren't wired to the reqs viaverifieslinks — so they show as unverified (part of the 311 lifecycle-coverage gaps). v0.1 burn-down = wire those links, then driveapproved → verified(a traceability-audit pass), after which v0.1 is cuttable.No artifact content changed — only
release-v0.1.0tags added + a planning doc.🤖 Generated with Claude Code