chore: rivet traceability hygiene — validate clean under 0.22.0#251
Open
avrabe wants to merge 2 commits into
Open
chore: rivet traceability hygiene — validate clean under 0.22.0#251avrabe wants to merge 2 commits into
avrabe wants to merge 2 commits into
Conversation
… CP links - CP-1/2/3 (control-structure): replace undeclared inverse link 'acted-on-by' with the forward 'acts-on' link on the acting controllers (CTRL-1/2/3/6/7); rivet resolves the 'acted-on-by' backlink automatically. - SG-1..6 (safety-case): goal-type 'top-level' -> 'system-level' (product safety goals are system-level per the schema's allowed values). - SOL-3/4/5/6/7/8 (safety-case): evidence-type 'test' -> 'test-report' (SOL-1 analysis / SOL-2 formal-proof already valid). - verification.yaml: TEST-* -> REQ-* links changed from 'satisfies' to 'verifies' so every REQ-1..18 has an incoming 'verifies' backlink grounded in a real cargo test / Z3 / Rocq / dogfood / fuzz target. Kept a 'satisfies' backlink on TEST-CSE-SAFETY-GUARDS -> REQ-2 so REQ-2 stays covered by both a satisfier and a verifier (it has no other design-decision/feature satisfier). - Stripped absolute local paths (/Users, /opt/homebrew) from the run: commands so committed artifacts contain no machine-specific paths. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
rivet 0.22.0 tightened the allowed status enum; loom's safety artifacts still used domain values it rejects (23 validate ERRORs on main). Map to the nearest lifecycle value: - 16x TEST-* 'passing' -> 'verified' (verification executed and passing) - 4x hazard 'MITIGATED' -> 'accepted' (residual risk accepted post-mitigation) Combined with the earlier hygiene commit (CP link direction, SG goal-type, SOL evidence-type, REQ verifies backlinks, absolute-path strip), rivet validate now PASSes: 0 errors, 33 non-failing warnings (down from 23/63). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Makes
rivet validatePASS on loom (was 23 errors / 63 warnings on main → 0 errors / 33 warnings). No code touched —safety/**only.Fixes
acted-on-bylink → moved to the correct forwardacts-ondirection on the acting controllers; rivet derives the backlink. Same graph, schema-valid.goal-type: top-level(invalid) →system-level.evidence-type: test(invalid) →test-report(SOL-1 analysis / SOL-2 formal-proof left as-is).verifiesbacklink → the existing TEST-* artifacts linked withsatisfies; switched the 23 REQ-targeted links toverifies(each grounded in a real cargo test / Z3verify::/ Rocq proof / dogfood / fuzz target — no fabricated coverage).passing→verified, 4x hazardMITIGATED→accepted./Users,/opt/homebrew) fromverification.yamlrun:commands → repo-relative + env-driven.Review note
The 4 hazard
MITIGATED→acceptedremaps are a safety-posture wording choice (the 0.22.0 enum has nomitigated). Flag if you'd preferverifiedor a schema extension instead.Residual 33 warnings are coverage nudges / unknown-field INFO (e.g.
feature.method), non-failing — a separate follow-up if we want them zero.