oficina / docs Public

Spec: park the question of Docs' own markup

Paul has paused design-system questions until rastrillo's settles and
estilo is real. My §10.1.1 had just answered one of them, so it is marked
parked rather than left reading as settled.

Estilo's own components stay settled -- estilo ships its own styling, so
that row was never the parked question. rastrillo's partials emit what
they emit. Only Docs' own markup waits.

Nothing is blocked: plans 1 and 2 are a Rust crate and a wazero host and
write no markup at all.

The instruction that matters is the last line -- change nothing and let
no task quietly decide it. A parked question an implementer resolves in
passing is worse than an open one, because it reads as settled to the
next person and nobody knows it was chosen rather than ruled.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011F5CivVm4CmL9ByfSSAaXA

Paul Campbell pushed by paul@keymail.dev 1 month ago 1cf49418b52f7b86b4aa34441681bce6633174f9 parent f2b1952

1 file changed, +16 −5

docs/superpowers/specs/2026-08-30-docs-design.md +16 −5

No CI script — run details

Intent

full ledger: plan-rust-core

diff --git a/docs/superpowers/specs/2026-08-30-docs-design.md b/docs/superpowers/specs/2026-08-30-docs-design.md

index 49521f0..c33efda 100644

--- a/docs/superpowers/specs/2026-08-30-docs-design.md

+++ b/docs/superpowers/specs/2026-08-30-docs-design.md

@@ -580,11 +580,22 @@ consuming rastrillo's CSS and estilo does not do that.

**The settled split:**

-| Markup | Spelling | Styled by |

-|---|---|---|

-| Estilo's own components | Attribute grammar | Estilo |

-| Docs' own markup | Attribute grammar | Estilo |

-| rastrillo partials we consume | Whatever rastrillo emits — classes today | rastrillo |

+|---|---|---|---|

+**The middle row is parked, deliberately** (Paul, 2026-08-30): design-system

+questions wait until rastrillo's design system settles and estilo is real.

+Docs writes no markup yet — plans 1 and 2 are a Rust crate and a wazero host

+— so nothing is blocked, and answering it now would mean converging on a

+decision that is about to be made upstream.

+**Until it is decided: change nothing, and let no task quietly decide it.** A

+parked question that an implementer resolves in passing is worse than an open

+one, because it looks settled to the next reader and nobody knows it was

+chosen rather than ruled.

Estilo ships its own components *and their styling*, so attribute-grammar

components styled by estilo are not interim anything — that is just estilo's