29 29 <
p><
strong>Implementation roadmap · 2026-07-11</
strong></
p>
30 30 <
h1>The System</
h1>
31 -<
p><
a href=
"../specs/2026-07-11-the-system-design.html">Design spec</
a></
p>
32 -<
p>Eight independently green phases keep the hard rename, governance kernel, document workflows, and final integration reviewable.</
p>
31 +<
p><
a href=
"../specs/2026-07-11-the-system-design.html">Original design spec</
a> · <
a href=
"../specs/2026-07-15-the-system-rich-markdown-design.md">Rich Markdown design amendment</
a></
p>
32 +<
p>Ten independently green phases keep the hard rename, governance kernel, rich document migration, rendering, workflows, and final integration reviewable.</
p>
33 +<
p>Phases 1–5 are complete. Phase 6 begins the approved replacement of their authored-HTML and shared-CSS assumptions without rewriting completed history.</
p>
35 36 <
section class=
"phase">
131 132 <
section class=
"phase">
132 -<
h2>Phase 6 · Spec authoring and browser review</
h2>
133 -<
p><
strong>Outcome:</
strong> brainstorming produces validated brutal HTML specs and separately editable spec-owned mockups.</
p>
133 +<
h2>Phase 6 · Rich Markdown bundle kernel migration</
h2>
134 +<
p><
strong>Outcome:</
strong> doctor, initialization, runtime governance, and shared validation understand Markdown document bundles instead of authored HTML files.</
p>
136 -<
li>Migrate brainstorming through <
code>system-documents</
code>.</
li>
137 +<
li>Replace flat authored-HTML paths with typed <
code>
<ID
>-
<slug
>/index.md</
code> bundle discovery and validation.</
li>
138 +<
li>Add the required Markdown/frontmatter parsing dependencies and explicit rich-profile candidate checks.</
li>
139 +<
li>Replace the <
code>system-documents</
code> authority's HTML contract with the canonical bundle and rich Markdown contract before downstream workflows delegate to it.</
li>
140 +<
li>Preserve source-ordered arbitrary frontmatter while retaining strict known graph semantics.</
li>
141 +<
li>Extend spec ownership approval to every existing file in a spec bundle while allowing validated new bundles and missing assets.</
li>
142 +<
li>Guard recognizable shell mutation across complete spec bundles.</
li>
143 +<
li>Stop creating project-local <
code>system.css</
code>; update config/schema versions and remove the obsolete machine-owned file only through approved initialization upgrade.</
li>
144 +<
li>Update doctor, initialization, runtime notices, and tests around the new structure.</
li>
146 +<
h3>Out of scope</
h3>
147 +<
p>Browser rendering and authoring workflow migration.</
p>
148 +<
h3>Verification</
h3>
149 +<
p>Bundle discovery, IDs, slugs, frontmatter order, graph diagnostics, ownership approve/deny/cancel, shell advisory coverage, initialization upgrades, source preservation, and retained runtime/task/mockup suites.</
p>
151 +<
p>The project has one coherent Markdown bundle model, doctor and runtime remain useful, and no browser or workflow depends on an unfinished renderer.</
p>
154 +<
section class=
"phase">
155 +<
h2>Phase 7 · Shared single-document and book renderer</
h2>
156 +<
p><
strong>Outcome:</
strong> users can open one document or the complete project dossier through one rich Markdown article pipeline.</
p>
159 +<
li>Add the unified/remark/rehype renderer for GFM, frontmatter, footnotes, definition lists, alerts, raw HTML, Mermaid, TeX, highlighting, anchors, and collapsed in-document contents.</
li>
160 +<
li>Render every frontmatter field in source order through the accepted compact summary and collapsed ledger.</
li>
161 +<
li>Copy complete bundle trees into temporary output and keep cross-document and asset links working.</
li>
162 +<
li>Add calm automatic Nugu light/dark styling inherited by every generated component.</
li>
163 +<
li>Add single-document and book shells around identical article HTML.</
li>
164 +<
li>Add graph references/backlinks, grouped navigation, previous/next movement, and generated full-text search.</
li>
165 +<
li>Add thin <
code>/system-view</
code> and <
code>/system-book</
code> prompts plus a rendering skill and cross-platform browser-opening CLI.</
li>
167 +<
h3>Out of scope</
h3>
168 +<
p>Spec, roadmap, plan, implementation, or issue authoring migration.</
p>
169 +<
h3>Verification</
h3>
170 +<
p>Identical article output across modes, every rich syntax feature, nested metadata, raw HTML, local/remote/cross-bundle links, inline mockups, body-content search, source hashes, opener platforms, Chromium, and Firefox.</
p>
172 +<
p>Rendering is independently useful and read-only while existing authoring skills remain unchanged.</
p>
175 +<
section class=
"phase">
176 +<
h2>Phase 8 · Spec authoring and browser review</
h2>
177 +<
p><
strong>Outcome:</
strong> brainstorming produces validated Markdown spec bundles with separately editable accepted mockups and consistent browser review.</
p>
180 +<
li>Migrate brainstorming through the bundle-aware <
code>system-documents</
code> authority.</
li>
137 181 <
li>Add thin <
code>/system-spec</
code> prompt.</
li>
138 -<
li>Allocate spec IDs and write semantic HTML linked to shared CSS.</
li>
139 -<
li>Persist only accepted mockups as adjacent compliant assets.</
li>
140 -<
li>Add cross-platform shell-free browser opener script.</
li>
141 -<
li>Print source path and ask before opening; never auto-open browser/editor.</
li>
182 +<
li>Allocate spec IDs and write canonical <
code>index.md</
code> using the rich profile.</
li>
183 +<
li>Persist only accepted mockups as owned HTML inside the spec bundle.</
li>
184 +<
li>Link mockups relatively and upgrade them to isolated inline previews during rendering.</
li>
185 +<
li>Print the source path and offer <
code>/system-view</
code> after authoring.</
li>
143 187 <
h3>Out of scope</
h3>
144 188 <
p>Roadmaps, plans, implementation, and issues.</
p>
145 189 <
h3>Verification</
h3>
146 -<
p>Workflow contracts, generated fixtures, approval behavior, mockup ownership, opener argv/platform tests, and generic mockup regressions.</
p>
190 +<
p>Workflow contracts, generated bundle fixtures, approval behavior, mockup ownership, single/book visual consistency, and generic mockup regressions.</
p>
147 191 <
h3>Boundary</
h3>
148 -<
p>An approved idea can complete the full design/spec review loop while later lifecycle stages remain on existing behavior.</
p>
192 +<
p>An approved idea completes the full design/spec review loop while later lifecycle stages remain on existing behavior.</
p>
151 195 <
section class=
"phase">
152 -<
h2>Phase 7 · Roadmap, plan, and implementation lifecycle</
h2>
153 -<
p><
strong>Outcome:</
strong> approved specs move through HTML roadmaps/plans into execution by PLAN-ID.</
p>
196 +<
h2>Phase 9 · Roadmap, plan, and implementation lifecycle</
h2>
197 +<
p><
strong>Outcome:</
strong> approved specs move through Markdown roadmap and plan bundles into execution by PLAN-ID.</
p>
156 -<
li>Migrate writing-roadmaps and writing-plans to validated HTML, exact metadata, and project-local paths.</
li>
200 +<
li>Migrate writing-roadmaps and writing-plans to validated bundles, exact metadata, and project-local paths.</
li>
157 201 <
li>Add <
code>/system-roadmap</
code>, <
code>/system-plan</
code>, and <
code>/system-impl</
code> prompts.</
li>
158 -<
li>Update reviewer prompts and downstream skills to read HTML.</
li>
202 +<
li>Update reviewer prompts and downstream skills to read rich Markdown bundles.</
li>
159 203 <
li>Resolve plans by ID and execute one spec or one roadmap phase with existing checkpoints.</
li>
204 +<
li>Offer consistent single-document or full-book review after authoring.</
li>
161 206 <
h3>Out of scope</
h3>
162 207 <
p>Issue capture.</
p>
163 208 <
h3>Verification</
h3>
164 -<
p>Prompt delegation, metadata/reference fixtures, phase boundary tests, plan execution resolution, report-only review, and full workflow-skill tests.</
p>
209 +<
p>Prompt delegation, metadata/reference fixtures, phase boundary tests, plan execution resolution, report-only review, rendering consistency, and full workflow-skill tests.</
p>
165 210 <
h3>Boundary</
h3>
166 211 <
p>The primary spec-driven development lifecycle is complete and CI-green.</
p>
169 214 <
section class=
"phase">
170 -<
h2>Phase 8 · Issue memory and integration hardening</
h2>
171 -<
p><
strong>Outcome:</
strong> defect capture completes the system and every spec contract is verified.</
p>
215 +<
h2>Phase 10 · Issue memory and integration hardening</
h2>
216 +<
p><
strong>Outcome:</
strong> defect capture completes the system and every original and amended design contract is verified.</
p>
174 219 <
li>Add general-purpose <
code>system-issues</
code> skill and <
code>/system-issue</
code> prompt.</
li>
175 -<
li>Support empty spec references while the violated contract is unknown; preserve deduplication and sanitized evidence.</
li>
176 -<
li>Complete startup, doctor, graph, approval, resource discovery, rename, and package integration tests.</
li>
220 +<
li>Write issue bundles with empty spec references allowed while the violated contract is unknown.</
li>
221 +<
li>Preserve deduplication and useful evidence without limiting trusted repository content.</
li>
222 +<
li>Complete startup, doctor, graph, approval, rendering, resource discovery, rename, and package integration tests.</
li>
177 223 <
li>Update final current documentation and changelog.</
li>
178 -<
li>Run final typecheck, focused suites, real extension loading, static checks, and CI.</
li>
224 +<
li>Run final typecheck, focused suites, real extension loading, static checks, browser suites, and CI.</
li>
180 226 <
h3>Out of scope</
h3>
181 -<
p>Provider-specific research, Git sync, compatibility aliases, and historical document migration.</
p>
227 +<
p>Provider-specific research, Git sync, compatibility aliases, persistent publishing, browser editing, and historical <
code>docs/super/**</
code> migration.</
p>
182 228 <
h3>Verification</
h3>
183 -<
p>Issue workflow fixtures, complete behavioral-contract audit against the spec, no live old-path references outside the historical allowlist, and <
code>mise run ci</
code>.</
p>
229 +<
p>Issue workflow fixtures, complete behavioral-contract audit against both design specs, no live old-path references outside the historical allowlist, and <
code>mise run ci</
code>.</
p>
184 230 <
h3>Boundary</
h3>
185 -<
p>The full design is implemented under one public extension with no half-migration or legacy surface.</
p>
231 +<
p>The full amended design is implemented under one public extension with no half-migration or legacy authored-document surface.</
p>