One folder, one bounded contextLLM view

What was decided, and why

Every decision here is REASONED from the tests and rulings named in its reason.

The picks that moved here from the wiring report

PickDecidedWhy
Merge queueno queue; the 4 laws, our bot, CI on mainworks on every plan
Generated filesa file every pull request edits is never committed; Go commits one per context0 conflicts measured
Observabilityinside each contextyour model
dependency.yaml tooladopt; one per service, contexts say usesyour earlier pick; removing the last user must never delete a database by itself
Secret folder, own dependencies/{service}/{kind}/{name}; shared stay /{kind}/{name}two services cannot collide
Shared dependencies in a plain landscapeallowedone sender per platform
Email senderthe platform's domain; optional brand domain per platformworks before a brand exists
Report styleDurian Hypermediathe wiring report's look

Where the model meets older rulings (gap scan section 4)

Your 21 Nov message is newer, so it wins where they clash. Everywhere else the older ruling stays.

Older rulingDecidedKind
layers are the top folderslayers move inside the contextyour model wins
tests live under tests/, never beside codecontexts/<ctx>/tests/; same tier names; the house checks' globs change in the same stepyour model wins
docs at docs/domain/<context>/contexts/<ctx>/docs/; inner folders model/, architecture/, implementation/your model wins; model/ is the better name you asked for
problem id is snake_casestays: <ctx>_<id>ruling stays
no policy enginestays: a policy is a named role check plus the owner checkruling stays
user id passes through, never filled from the tokenstays: Scope carries the owner exactly as the caller sent it, after the guardruling stays
one migration table per servicestays for Go and Bun: ids are <ctx>/<timestamp>_<name>. .NET is trade-off 2ruling stays, one question
no domain eventsstays inside a context; only published integration events cross, through an outboxnarrowed
shared services run as their own servicesstays: the kernel holds the port, client, definitions and generators; the running engine is a shared serviceboth hold
observability only where Helm existsstays: the slot is empty in Helm-less templatesruling stays
worker is its own templateone app, several hosts: api, worker, cron, migrate, MCP; each still deploys as its own modulechanged
"module switch" namesone name: <ctx>.enabledchanged
no "organisation" word existsnot invented: Scope has room for a tenant, empty todayruling stays
  • Renaming a context: the display name can change any time. The folder name never does. A true rename is a new context, then retire the old one.
  • Links between owners inside one context: the owner id is in every child row from day 0. Whether they are database links follows the multi-region talk.

Decided from the proofs

QuestionDecidedWhy
A project per layer or per contextper context, in all fouryour model; built and run
Go: a module per contextno: a package tree in one moduleper-context modules conflict
.NET: host lock filenone, as in today's template0 conflicts without it
.NET: slower clean buildaccept; cache and test what changedyour model; one edit costs the same
How the kernel finds contextsgenerated at build timeno reflection; fails early
Switching off a needed contextrefusedno half-working app
Billinga context-like shared service, not a kernel engineonly some contexts need it
Marketing, feedback, flags engineslistmonk, Fider, OpenFeature with flagd filessection 6

The four laws

Explorer
  • 1. the path is the name
  • context.yaml2. a claim is a git conflict: a random id
  • 4. never edited once published
  • 2. one file per free name
  • 3. no file every pull request edits

What was not tested

AreaNot tested
Mergingthe bot as a GitHub Action or App; the automatic revert pull request; waiting for the pull request's own CI
All languagesthe docs framework on a context; real engines behind the ports; MCP over a real client in every language
Goa real Go app (none exists); SIT
Bunreal Postgres, Logto, regions with lag; two of four knip configs
.NETthe other zinc modules; Docker build; coverage gates; a breach of metric or cache-key names
Fluttertests on a device; the template app as workspace root; generated Dart signals
Servicesnone was installed; costs and efforts are estimates; licences need the lawyer list
Multi-regiona job across all owners; nothing was asked of that study
  • The proofs were written before some rulings were folded in. The Flutter proof still uses an "org" field and a "functional" test folder. The design follows the rulings, not the proof.