Skip to content

chore(rivet): mark shipped requirements as implemented#211

Merged
avrabe merged 1 commit into
mainfrom
chore/rivet-mark-implemented
Jun 2, 2026
Merged

chore(rivet): mark shipped requirements as implemented#211
avrabe merged 1 commit into
mainfrom
chore/rivet-mark-implemented

Conversation

@avrabe
Copy link
Copy Markdown
Contributor

@avrabe avrabe commented May 31, 2026

Brings rivet requirement statuses in line with what has shipped on main: 24 draft + 2 planned (SR-33, SR-35) → implemented via rivet modify --set-status. Diff is status-line-only (26 lines).

Basisimplemented = code exists and works (full test suite green; real components fused + executed under wasmtime by the runtime tests). Not verified (per-requirement formal verification is a separate pass).

  • SR-35 DWARF address remap → v0.16–v0.20 (DwarfHandling::Remap); in-tree witness oracle passes. Its stated verification is a cross-repo witness smoke that is not yet done, so implemented, not verified.
  • SR-33 cross-component stream fusion → v0.9.0 (P3 async — cross-component stream adapter (#94 sub-A) #141).
  • SR-31 multiply-instantiated detection → LS-M-5 (ls_m_5_*).
  • SR-19 deterministic output → LS-A-15.
  • SR-1..SR-25 parser / canonical-ABI / merger / adapter / wrapping subsystems → shipped across v0.1–v0.20.

Held at planned (honesty — not on main):

rivet validate error count unchanged (164 pre-existing schema-drift / broken-link errors; none introduced). Those pre-existing validation issues + tooling friction hit during this pass are filed upstream as pulseengine/rivet#353.

🤖 Generated with Claude Code

Brings the rivet traceability requirement statuses in line with what has
actually shipped on main. 24 draft + 2 planned (SR-33, SR-35) → implemented;
SR-34 and SR-36 deliberately held at `planned`.

Basis (status `implemented` = code exists and works, full test suite green;
NOT `verified` = per-requirement formal verification, which is a separate pass):
- SR-35 DWARF address remap → shipped v0.16–v0.20 (DwarfHandling::Remap,
  dwarf.rs); in-tree witness oracle passes. NB its stated verification is a
  cross-repo witness smoke that is NOT yet done — hence implemented, not verified.
- SR-33 cross-component stream fusion → v0.9.0 (#141).
- SR-31 multiply-instantiated detection → LS-M-5, ls_m_5_* regression test.
- SR-19 deterministic output → LS-A-15.
- SR-1..SR-25 (parser / canonical-ABI / merger / adapter / wrapping) →
  foundational subsystems shipped across v0.1–v0.20; exercised end-to-end by
  the wasmtime runtime tests (real components fused + executed).

Held at `planned` (honesty — not on main):
- SR-34 static stream validation: (i)/(iii) merged, (iv) is in the unmerged
  PR #210, (ii) bounded-capacity is N/A. Flip to implemented when #210 merges.
- SR-36 synthesised DWARF DIEs for adapters: DWARF Phase 3 (#144), not started.

`rivet validate` error count is unchanged (164 pre-existing schema-drift /
broken-link errors, none introduced by this change).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown

LS-N verification gate

⚠️ 36/38 verified — 2 missing regression tests

count
Passed (≥1 test, all green) 36
Failed (≥1 test failure) 0
Missing (no ls_*_NN_* test found) 2

Approved loss-scenarios.yaml entries are expected to have a
regression test named ls_<letter>_<num>_* (e.g. LS-A-11
ls_a_11_*). The gate runs each prefix via cargo test --lib --no-fail-fast and aggregates pass/fail/missing.

Failed LS entries

(none)

Missing regression tests
  • LS-R-13
  • LS-M-6

Updated automatically by tools/post_verification_comment.py.
Source of truth: safety/stpa/loss-scenarios.yaml.

@avrabe avrabe merged commit e13357b into main Jun 2, 2026
5 checks passed
@avrabe avrabe deleted the chore/rivet-mark-implemented branch June 2, 2026 05:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant