What diene is missing
86 points were checked across goals, concepts, rulings, templates, standards and your agenda decisions, each with its state. The big holes are not features: they are the standards, which today say the opposite of your model.
What blocks the top-level workspace
| Thing | Blocks workspace? | Where it is recorded |
|---|---|---|
| Durian Hypermedia, then the docs framework, then the word list (UL) | yes, by your ruling | your rulings |
| Where a context's docs live | yes | workspace's documentation standard |
| How main stays green without a queue | yes: the check, the bot, CI on main | gatekeeper runs on pull requests only |
| Generators before lints | yes | wiring report, point 2 |
| The context layout and the kernel | no: shared and the language bases | shared's layout standard |
| Logto | no | workspace's goals |
| Multi-region | no | 0 mentions in workspace or shared |
So you are half right: docs and Hypermedia block workspace. Logto and multi-region do not. The module system is mostly a shared-node change; workspace needs only 3 small parts of it.
The gaps that matter most
FROM DOCS and FROM CODE (the scan).
| Gap | State | Must be settled before |
|---|---|---|
| Layout standard says layers first | decided the other way | shared |
"Tests never beside code", and the house checks only look in tests/ and src/ | decided the other way; the checks would pass on nothing | shared |
Docs at docs/domain/<context>/ | decided the other way | workspace |
| Merging without a queue | open; designed and tested here | workspace |
| Rule for what may cross contexts (contract, events, ids) | partly | shared |
| Reads that join across contexts (lists, search, reports) | open | shared |
| Work that spans contexts (sagas, outbox) | partly | shared |
| Erasure and export per context | open | shared (the shape) |
| Pagination | open | shared |
| Idempotency on writes | partly | shared |
| Rename, split, merge, delete a context | open; rename decided here | shared |
| OpenAPI and generated clients per context | partly | language base |
| Hosts: cron, MCP; a Go API template | open | language base |
| Coverage, Docker and CI paths assume layer folders | decided; must change | language base |
| The signal port in the 4 interfaces libraries | open, not built | language base |
| Kernel contract test, blind-spot table | open; proven here, not built in a template | language base |
| Flag engine, server and client | partly; target ruled, not built | language base (the port) |
| Goals for the shared services | open | later |
The order of work
REASONED, on your rulings.
- Hypermedia, then docs, then UL. Your chain, unchanged.
- Workspace: docs inside the context, the merge check and bot, CI on main, generators first.
- Shared: the context standard, tests inside contexts with fixed check paths, the identity shape, events and outbox, the engine ports.
- Language bases: kernel, generated registration, layer guard, coverage paths, signal port, hosts, contract test.
- Later, into slots: multi-region values, the auth fork, the engines, then each app's move.
The order
Animation, 4 steps. Starts with: box dh "Hypermedia"; box docs "docs + UL"; box ws "workspace"; box sh "shared"; box lang "language bases". Connected: dh -> docs, docs -> ws, ws -> sh, sh -> lang. Families, one colour each: doc "docs chain" (dh, docs); node "template nodes" (ws, sh, lang). 1. Hypermedia first, then the docs framework and the word list. dh -> docs: format 2. Workspace takes only docs location, the merge check and generators first. docs -> ws: unblocks 3. Shared gets the context standard and the fixed shapes. ws -> sh: standard 4. Each language base gets the kernel and the folder. sh -> lang: kernel