One folder, one bounded contextLLM view

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

ThingBlocks workspace?Where it is recorded
Durian Hypermedia, then the docs framework, then the word list (UL)yes, by your rulingyour rulings
Where a context's docs liveyesworkspace's documentation standard
How main stays green without a queueyes: the check, the bot, CI on maingatekeeper runs on pull requests only
Generators before lintsyeswiring report, point 2
The context layout and the kernelno: shared and the language basesshared's layout standard
Logtonoworkspace's goals
Multi-regionno0 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).

GapStateMust be settled before
Layout standard says layers firstdecided the other wayshared
"Tests never beside code", and the house checks only look in tests/ and src/decided the other way; the checks would pass on nothingshared
Docs at docs/domain/<context>/decided the other wayworkspace
Merging without a queueopen; designed and tested hereworkspace
Rule for what may cross contexts (contract, events, ids)partlyshared
Reads that join across contexts (lists, search, reports)openshared
Work that spans contexts (sagas, outbox)partlyshared
Erasure and export per contextopenshared (the shape)
Paginationopenshared
Idempotency on writespartlyshared
Rename, split, merge, delete a contextopen; rename decided hereshared
OpenAPI and generated clients per contextpartlylanguage base
Hosts: cron, MCP; a Go API templateopenlanguage base
Coverage, Docker and CI paths assume layer foldersdecided; must changelanguage base
The signal port in the 4 interfaces librariesopen, not builtlanguage base
Kernel contract test, blind-spot tableopen; proven here, not built in a templatelanguage base
Flag engine, server and clientpartly; target ruled, not builtlanguage base (the port)
Goals for the shared servicesopenlater

The order of work

REASONED, on your rulings.

  1. Hypermedia, then docs, then UL. Your chain, unchanged.
  2. Workspace: docs inside the context, the merge check and bot, CI on main, generators first.
  3. Shared: the context standard, tests inside contexts with fixed check paths, the identity shape, events and outbox, the engine ports.
  4. Language bases: kernel, generated registration, layer guard, coverage paths, signal port, hosts, contract test.
  5. 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

  • docs chain
  • template nodes
HypermediaHypermediadocs + ULdocs + ULworkspaceworkspacesharedsharedlanguage baseslanguage basesformat
1Hypermedia first, then the docs framework and the word list.
1 / 4
All steps (4)