[strategist] planning: RFC #4002 phased delivery roadmap (docs/rfc-4002-phased-roadmap.md)

[kubestellar-hive]

Planning Artifact

Adds docs/rfc-4002-phased-roadmap.md (new file, only file touched): a phased delivery roadmap for RFC #4002 (re-entrant conversation-as-state turn model).

• Compatibility contract the re-entrant path must honor in every phase
• Phase 0 (spike/state inventory) → Phase 1 (contributor agents) → Phase 2 (background agents, integrates [v5] Adopt tool-approval as an explicit, ACMM-gated operation #4000) → Phase 3 (default), each with a measurable exit gate
• Version targeting: Phases 0–1 v5-compatible opt-in; 2–3 target v6; explicitly not a v5 GA blocker (refs [strategist] v5 GA readiness criteria are prose-only — define a trackable GA bar #5622)

Cluster claimed: RFC #4002 planning only — no source code, no overlap with open hold PRs #5634 (escalation ledger), #5628 (pin-off docs), #5625 (mutation ledger persist), #5559 (UPGRADE.md), #4032 (proxy auth).

Refs #5555, Refs #4002

---

Filed by strategist agent (ACMM L5 — hold-gated mode). Hold-gated: human review required.

— hive: agent=strategist backend=copilot model=claude-sonnet-4-6

[clubanderson]

CONCERNS: this doc now competes with the phased roadmap posted on issue #5555 (operator comment, 2026-09-02), and the two disagree on substance, not just numbering:

• Phase structure: this doc has Phases 0–3; the #5555 roadmap has Phases 0–5. This doc's Phase 1 (first live wiring on contributor agents) is the #5555 roadmap's Phase 3, and this doc omits that roadmap's Phase 1 (converging pkg/turn and pkg/convergence/mutation while still inert) and Phase 2 (a Promela/Spin model in src/formal/turn/ as a hard precondition before anything passes the edge channel) entirely — no formal-model step appears here at all.
• Kill criterion: the #5555 Phase 0 has an explicit exit ramp (close #4002 if TurnLoss data shows Producing is a small fraction of Interruptions); this doc's Phase 0 gate is only 'report reviewed; go/no-go recorded'.
• Version targeting conflicts: this doc sends its Phases 2–3 to v6 ('not a v5 GA blocker'); the #5555 roadmap is explicitly v5-line delivery (live wiring on v5 only, v4 untouched).
• Scope deltas: this doc folds #4000 in ('should not ship separately') and already exercises handoff in its Phase 1 gate ('handoff exercised at least once across a process restart'); the #5555 roadmap defers handoff to Phase 5 'only if still wanted' and does not subordinate #4000.

Two competing roadmaps for the same RFC is worse than either alone. Suggest either rewriting this file to be the in-repo rendering of the #5555 roadmap once the operator accepts it, or closing this PR in its favor. Verdict: CONCERNS — do not merge as-is.

[clubanderson]

Fixes #5555

[clubanderson]

Reviewed against the #5555 dispatch plan. I pushed a docs-only fix so the roadmap now names the already-shipped stages 1–2 and documented step-3 handoff eval, keeps the compatibility contract, makes Phase 2 cover all background agents, and adds measurable Phase-2 gates. go build ./... passed before the docs-only adjustment; PR comment links Fixes #5555.

[kubestellar-prow]

LGTM label has been added.

Details

Git tree hash: 19736b62c75919e401d620a3d249e3d36dde3ee8

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from clubanderson. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[clubanderson]

Re-reviewed after my amended docs-only fix. The roadmap now matches #5555's requested dispatch plan, including delivered investigation stages, all-background Phase 2, compatibility contract, and measurable gates. go build ./... passed before the docs-only changes.

[kubestellar-prow]

LGTM label has been added.

Details

Git tree hash: fe072de26a73702b1511daa41831c78ead145591

[github-actions]

Thank you for your contribution! Your PR has been merged.

Check out what's new:

• KubeStellar Console — Live multi-cluster dashboard
• Marketplace — Community extensions
• Knowledge Base — Troubleshooting and how-tos

Stay connected: Slack #kubestellar-dev | Multi-Cluster Survey