plan(roadmap): defer TRACE-P02 to v1.134 — v1.133 is the OCI/release arc - #341
Merged
Conversation
v1.133's scope is the OCI/release arc (OCI-P02 no_std cascade, OCI-P04 WIT namespace, REL-P01 draft-then-finalize), which is implementation-complete and waiting only on CI. TRACE-P02 (drive implemented->verified from the gate's own per-artifact result) is independent of that arc and large enough to warrant its own release rather than holding the OCI arc behind it. Deliberate scope move, logged in the artifact itself rather than done silently. No code, no status change: TRACE-P02 stays `proposed`. v1.133 scope after this: OCI-P02, OCI-P04, REL-P01. v1.134 scope after this: OCI-P03, TRACE-P02. `rivet validate` PASS. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HvusAXYbHLyv3uTzfBcMbG
The push that would have triggered CI landed during the outage (Actions was in major_outage 15:22Z-00:0xZ; zero runs were created repo-wide for hours), so no run exists for this branch. Empty commit to generate a fresh synchronize event. Squash-merge drops it from main. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HvusAXYbHLyv3uTzfBcMbG
avrabe
enabled auto-merge (squash)
August 7, 2026 01:29
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
Moves
SWREQ-FALCON-TRACE-P02fromfalcon-v1.133.0tofalcon-v1.134.0.v1.133 scope after this: OCI-P02, OCI-P04, REL-P01
v1.134 scope after this: OCI-P03, TRACE-P02
Why
v1.133 is the OCI/release arc — the no_std cascade conversion, the WIT namespace
rename, and draft-then-finalize release ordering. That arc is
implementation-complete and waiting only on CI.
TRACE-P02 (drive
implemented→verifiedfrom the verification gate’s ownper-artifact result) is independent of it, and is a large sweep in its own right:
of the 140 sw-reqs TRACE-P01 backfilled, 137 link only to verifiers that are
themselves unpromoted. Holding the OCI arc behind that sweep buys nothing.
This is a deliberate scope move, logged in the artifact itself rather than
done silently — per the release-planning rule that deferral is a scope decision,
surfaced, not quiet.
Not in this PR
No code. No status change — TRACE-P02 stays
proposed. This is only therelease:field and its rationale, so the two-commit rule is not in play.Evidence
rivet validate→ PASS (352 warnings, all pre-existing)the complete set
Correction
This PR originally carried
Verify-Filter: (has-tag "traceability"). That filtermatches 0 of 195 sw-verification artifacts —
traceabilityis a tag onsw-reqs, not on verifications — so it would have passed the gate vacuously
(
0/0 passed, rendered with a ✅).The override is removed; this PR now runs the default
(has-tag "falcon")sweep. The underlying fail-open is fixed separately in #342.
🤖 Generated with Claude Code
https://claude.ai/code/session_01HvusAXYbHLyv3uTzfBcMbG