Back to Plate

Slate v2 Package End-State Roadmap Polish

docs/plans/2026-04-06-slate-v2-package-end-state-roadmap-polish.md

53.0.62.4 KB
Original Source

Slate v2 Package End-State Roadmap Polish

Supporting plan. For current queue and roadmap truth, see master-roadmap.md.

Goal

Use a ralplan-style consensus pass to tighten docs/slate-v2/package-end-state-roadmap.md into the cleanest honest package gate in the v2 doc stack.

Scope

  • improve structure and readability
  • sharpen done/next/later visibility
  • reinforce the doc's ownership boundaries
  • keep package queue truth aligned with the patched phase model

Non-Goals

  • no new package strategy
  • no fake completeness
  • no new phase ladder here
  • no changes to public API claims without evidence

Progress

  • context snapshot created in .omx/context/
  • source doc reread after the phase-model patch
  • consensus shape chosen: status-first polish without changing strategy
  • polish applied to docs/slate-v2/package-end-state-roadmap.md
  • verification passed:
    • pnpm exec prettier --check docs/slate-v2/package-end-state-roadmap.md docs/plans/2026-04-06-slate-v2-package-end-state-roadmap-polish.md .omx/context/slate-v2-package-end-state-roadmap-polish-20260406T192614Z.md
    • grep confirmed the key top-level sections exist:
      • Current Status Snapshot
      • Current Package Queue
      • Appendix: Fresh ProseMirror + Lexical Scan

RALPLAN-DR Summary

Principles

  • truth over polish theater
  • queue visibility beats exhaustive scroll depth
  • keep package ownership sharper than phase narration
  • preserve the full TS/API and appendix evidence instead of hiding it

Decision Drivers

  • readers need the live queue near the top
  • the doc must stay the single package gate after the phase-model patch
  • polish must reduce drift and repetition without inventing new strategy

Viable Options

  • minimal polish: keep structure, tighten prose only
  • status-first polish: bring live phase/queue snapshot to the top, keep package sections intact, demote the appendix
  • aggressive restructure: split appendix or trim API inventories into separate docs

Chosen Option

  • status-first polish
  • reason: best signal gain for the least strategic churn

Architect / Critic Read

  • Architect steelman: do not let “polish” become a hidden strategy rewrite or a doc split that weakens the package gate
  • Critic verdict: approve if the queue moves up, appendix is clearly subordinate, and top-level redundancy gets trimmed