Repository navigation
id: design: style assertion vocabulary (from #5679) #5850
Description
Summary
Follow-on design ticket from #5679 — its decomposition sketch names this as a separate design, and the parent's acceptance requires these tickets to be filed and linked. Filed in the 2026-11-04 gap pass (WS-F) so the design work exists and can be prioritised on its own merits; implementation timing is a separate decision, possibly months out.
What this design must settle
Colour, typography, spacing, and state roles and tokens: the assertion vocabulary that replaces per-target styling.
Context from the parent
The parent design fixes the semantic markup + style-assertion model by which programs-as-websites render across web, native, and custom targets. The parent issue carries the surrounding decisions this ticket must not re-decide; where this ticket's answer would change a parent decision, record that explicitly rather than silently forking it.
Decision record expected
Close this design with a recorded decision (on this issue or in a doc/ record linked from it): the chosen shape, the alternatives rejected and why, and the invariants implementation must hold. If the design splits further, file the splits and link them here rather than growing this issue.
Relations
Parent: #5679. Programme: epic #2056. Filed by WS-F (2026-11-04 ID design gap & expansion pass).
Activity
developing-today commentedon Nov 5, 2026
CODE-1533
dezren39 commentedon Nov 5, 2026
🤖 Agent note · done (triage)
Triage findings (verified fresh 2026-11-05 via
gh):task/triage,queue/queued,app/id. No hard-stop labels (held,user/owned,do-not-merge,do-not-auto-edit) and nouser/review/user/escalated. Only comment is an automated Kaneo cross-link — no competing work or decision on the issue.doc/record linked from it): chosen vocabulary shape, alternatives rejected and why, and the invariants implementation must hold. Further splits get filed as their own tickets and linked here.Triage complete for task 10253; issue #5850 stays open for the design decision.