/ work / decouple-the-views
Decouple the views
0 of 5 units done. Five audiences across the surfaces they touch is not writeable by hand. The store is already data-driven at the content layer and hand-written at the view layer, and that seam is what the memo is pointing at: JSON configuration, components, and the same generate-and-check discipline coding.sgit.ai and nfrs.sgit.ai both teach.
This workstream came out of a memo. Five audiences, decoupled views, and the version the board can read, 2026-09-16 — kept verbatim, read into a brief, and broken into the units below.
Queued3
Three thousand lines, of which the page shells and the block renderers are the part five audiences would multiply. Extract those first; leave the markdown renderer and the gate alone.
Blocked on DV-2.memo 2026-09-16The store's own idiom, applied to views: a register with no file and a file with no register entry both fail the build, the way the reviews already do.
Blocked on DV-3.memo 2026-09-16The acceptance test for the whole workstream. If adding an audience is still a code change, the refactor did not land.
Blocked on DV-4, QB-4.memo 2026-09-16Up Next1
This is the decision the rest depends on and it has a hard constraint on it. Every selling page on this site opens no connection and a build check fails the release if one does. Components that fetch their own configuration would negotiate with that rule. Components that are rendered at build from the same JSON would not, and would still give the memo what it asked for.
The project lead, in conversation · memo 2026-09-16In Progress1
coding.sgit.ai measures its conventions by counting the code rather than asserting them; nfrs.sgit.ai runs one rule — link the measurement, never restate it, generate or date every number — and fails its build otherwise. This store already runs both of those; what is not yet written down is which of their component conventions apply to a site that ships no framework.
memo 2026-09-16Done0
—