From the 2026-07 traceability audit:
- Only ~3% of artifacts carry a
release: field, so rivet release status history is queryable only from v1.114 onward. Backfill: every verified/implemented artifact gets the release it actually shipped in (git-history-derived, scriptable via git log --follow on each artifact file + tag containment).
- ~54 verification steps are whole-crate
cargo test -p X (weak requirement→test traceability) vs 18 named-test steps. Convert opportunistically: when an artifact is touched, its steps must name specific tests (the gate already fails named tests that match 0 — pulseengine.eu#89 — so named steps are self-checking).
Enforcement follow-up: once backfill is done, make the verification gate WARN on new whole-crate-only artifacts (then FAIL after a grace period).
Not a single big-bang PR — do the backfill scripted + review, the step conversion incrementally with a gate warning to stop regression.
From the 2026-07 traceability audit:
release:field, sorivet release statushistory is queryable only from v1.114 onward. Backfill: every verified/implemented artifact gets the release it actually shipped in (git-history-derived, scriptable viagit log --followon each artifact file + tag containment).cargo test -p X(weak requirement→test traceability) vs 18 named-test steps. Convert opportunistically: when an artifact is touched, its steps must name specific tests (the gate already fails named tests that match 0 — pulseengine.eu#89 — so named steps are self-checking).Enforcement follow-up: once backfill is done, make the verification gate WARN on new whole-crate-only artifacts (then FAIL after a grace period).
Not a single big-bang PR — do the backfill scripted + review, the step conversion incrementally with a gate warning to stop regression.