Skip to content

docs(roadmap): 0.9 = soundness + introspection - #285

Merged
unbalancedparentheses merged 1 commit into
mainfrom
docs/roadmap-0.9-soundness
Nov 17, 2026
Merged

unbalancedparentheses merged 1 commit into
mainfrom
docs/roadmap-0.9-soundness

Conversation

@unbalancedparentheses

Copy link
Copy Markdown
Contributor

Decided 2026-11-17: every soundness item that is ready goes into 0.9.

Docs only.

@github-actions

Copy link
Copy Markdown

🤖 Claude Code Review

Review: PR #285 (ROADMAP re-scope of 0.9)

This PR changes only docs, so there are no correctness or concurrency concerns. The review covers internal consistency of the roadmap.

Inconsistencies to fix

1. The admission package fallback release disagrees with itself.

  • ROADMAP.md, Releases section, 0.9 bullet: "implementation in 0.9 if it is ready, else 0.10".
  • The next lines say "0.10: supervising, OTP-complete" (no admission work listed) and "0.11 (or earlier, see 0.9): the admission package…".
  • Status section (~L59): "ships as soon as its design and model pass review", which names no fallback release.

Choose one fallback, 0.10 or 0.11, and use it in all three places. If 0.10 is the fallback, 0.11 should no longer be titled as the admission release. If 0.11 is the fallback, change "else 0.10" to "else 0.11".

2. The G7 table row is probably stale.

  • The CHANGELOG and both 0.9 bullets now place {shutdown, Term} exits (G7) in 0.9.
  • The diff updates G11 but does not touch the G7 row.
  • Check that G7, and G1 and G2, say 0.9 (unified start) / 0.9 in the gap table, as G8 already does.

3. handle_continue appears without explanation (~L115).

  • The new 0.9 bullet adds handle_continue to the unified start API list.
  • The old 0.10 bullet did not list it.
  • If unified-start.md already covers it, that's fine. If not, it is a scope addition that the CHANGELOG entry doesn't mention.

4. The "one theme each" principle no longer holds.

  • ROADMAP.md (~L120) says "Releases are kept small: one theme each".
  • 0.9 now carries soundness, unified start, introspection/console and, conditionally, admission.
  • Either reword the principle, for example to allow paired themes, or acknowledge the exception in the 0.9 bullet. Otherwise the document contradicts itself.

Minor

  • Mismatched soundness wording. The status section (~L56) says "the remaining unchecked guarantees, fuzzer oracles and race-only mutants". The Releases section says "the remaining semantics, fuzzer and mutation gaps". Use one phrasing so readers don't wonder whether they are different scopes.
  • Issue numbers missing from Releases. The status section cites fix: keep user code off the shared deadline-service thread #282 and feat(verification): trace validation for the Coordinator model #283, but the Releases section describes the same items without them. Add the issue numbers for traceability.
  • G11 row format (L273). The value "with the admission package (rank 14; designed in 0.9)" breaks the column's release-number format. Something like 0.10/0.11 (admission package, rank 14) would fit better once item 1 is resolved.
  • Status bullet length. The "Next release, 0.9" status bullet is now one very long paragraph. Splitting it into sub-bullets (Soundness / Admission / Introspection) would read better.
  • CHANGELOG placement. A roadmap-only change in CHANGELOG.md is unusual if the changelog is user-facing. Keep it only if that is the project convention, which earlier entries like the tla-traces fix suggest is fine for internal changes.

Otherwise the re-scoping is clear, and moving unified start ahead of the dynamic supervisor is sensible, since 0.10 now builds on it.


Automated review by Claude · claude-opus-5-5 · custom prompt · 3.4k in / 2.3k out · ~$0.06

@github-actions

Copy link
Copy Markdown

🤖 Gemini Code Review

Looks good. The documentation updates in CHANGELOG.md and ROADMAP.md are clear and consistent.


Automated review by Gemini · gemini-4-argon · custom prompt · 2.4k in / 1.0k out · ~$0.02

@github-actions

Copy link
Copy Markdown

🤖 Grok Code Review

Docs-only PR. The version story for the admission package is inconsistent, and the gap table may not match the new 0.9 scope.

Admission target disagrees with itself

  • ROADMAP.md ~58–59: designed in 0.9 and “ships as soon as its design and model pass review” (no release).
  • ROADMAP.md ~115: implementation in 0.9 if ready, else 0.10.
  • ROADMAP.md ~117: still listed under 0.11 (“or earlier, see 0.9”).
  • ROADMAP.md ~273 (G11): “with the admission package … designed in 0.9”, so the control lane no longer has a release.

Pick one fallback (0.10 or 0.11) and use it in the 0.9 blurb, the 0.10/0.11 bullets, G11, and the changelog. “Ships as soon as review passes” also fights the “one theme per release” rule a few lines later.

Gap table vs narrative

The changelog and 0.9 sections move G1, G2, G7, and G8 into 0.9, but this diff only retargets G11. G8 was already 0.9 (unified start) in the shown context. If the G1/G2/G7 rows still say 0.10, they are now stale. Update them in this PR.

No code, concurrency, or lifecycle issues in the diff.


Automated review by Grok (xAI) · grok-4.7 · custom prompt · 3.5k in / 2.3k out · ~$0.02

@github-actions

Copy link
Copy Markdown

🤖 Codex Code Review

No findings. This PR only updates ROADMAP.md and CHANGELOG.md to reflect release priorities; it changes no Rust code or runtime behavior.

The documentation changes look consistent. Tests aren’t needed for this documentation-only update.


Automated review by OpenAI Codex · gpt-6.1-sol · custom prompt · 24.5k in / 185 out · ~$0.03

@github-actions

Copy link
Copy Markdown

🤖 Kimi Code Review

  • Minor documentation inconsistency — ROADMAP.md:120: The roadmap still says releases have “one theme each,” but revised 0.9 (ROADMAP.md:53-67 and :115) combines soundness, introspection, the unified start API, and admission design. Consider rewording the process statement or explaining the broader 0.9 theme.

Otherwise, the changelog, release sequence, and G11 admission-package timing are consistent. This is documentation-only, with no code, concurrency, or runtime impact.


Automated review by Kimi (Moonshot AI) · kimi-k3.1-pro · custom prompt · 2.3k in / 1.2k out · ~$0.02

@github-actions

Copy link
Copy Markdown

🤖 DeepSeek Code Review

This PR is documentation-only (CHANGELOG.md, ROADMAP.md), so the actor-framework runtime review categories don’t apply. The roadmap changes are internally consistent: soundness + introspection move into 0.9, unified start and G7 move into 0.9, G11 follows the admission package, and the 0.10/0.11 plans are updated accordingly.

Minor docs nit:

  • CHANGELOG.md:5-7 describes the admission package as only “designed during 0.9,” while ROADMAP.md:58-59 says the package “ships as soon as its design and model pass review,” and the 0.9 release plan says “implementation in 0.9 if it is ready, else 0.10.” Align the changelog wording so it doesn’t understate the possible 0.9 implementation.
  • CHANGELOG.md:5-7 is roadmap metadata rather than a user-facing product change. Changelogs usually track product behavior; consider moving this note out of the changelog or clearly labeling it as roadmap-only.

Otherwise LGTM; no runtime, concurrency, safety, or performance impact.


Automated review by DeepSeek · deepseek-v4-pro · custom prompt · 2.4k in / 5.5k out · ~$0.02

@unbalancedparentheses
unbalancedparentheses added this pull request to the merge queue Nov 17, 2026
Merged via the queue into main with commit c28b961 Nov 17, 2026
42 checks passed
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