Phase Status Sync

Slice Advancement Rule

When the previous roadmap next-step has already been consumed by code, tests, and reference docs, use the phase sync to advance the active slice explicitly rather than leaving the roadmap one step behind.

Apply this rule when:

• the active phase is unchanged
• the last near-term roadmap next-step is now part of the current baseline
• the remaining drift is mostly in project-status and roadmap wording rather than long-term strategy

In that case, sync the files this way:

• docs/project-status.md: absorb the newly-stable hardening or support work into the current baseline
• docs/roadmap.md: promote the real next slice, next letter, or next narrow workflow step
• docs/product-strategy.md: leave unchanged unless the long-term strategy itself changed
• docs/project-plan.md: leave unchanged unless planning navigation changed

Do not leave an already-completed hardening step described as the current next slice just because the active phase has not changed.

Release-Line Planning Model

After the foundation baseline, do not assume future planning must follow fixed Week N -> Slice A/B/C calendar buckets. Use this model instead:

• product-strategy: owns long-term strategic tracks and why they matter
• roadmap: owns the active release-line milestone, active slice, candidate next slices, and stop condition
• project-status: owns current implementation reality, current tag baseline, verification evidence, and known gaps
• project-plan: stays a short planning entry page

When a future planning task asks what to do next:

• pick the narrowest evidence-backed slice from the strategic tracks
• state which release-line milestone or planning boundary it belongs to
• define the slice stop condition before widening scope
• avoid creating another long week-by-week plan unless the user explicitly asks for one

Repo Anchors

• docs/project-status.md
• docs/roadmap.md
• docs/project-plan.md
• docs/product-strategy.md
• docs/contributing/documentation-maintenance.md
• docs/contributing/release-versioning.md
• ../../../CHANGELOG.md

Output Shape

• State the current phase or drift type first.
• List which of project-status, roadmap, project-plan, and product-strategy changed and why.
• Call out any remaining mismatch, or explicitly say the planning docs are aligned.