field notes codename
24 notes filed under MERIDIAN, newest first. Same rules as the rest of the pile: a codename, a theme, and no internals.
Everybody has decision templates: how a group picks among options, who may act for whom, how a bridge between two groups gets authorised. Those templates usually live in prose, and prose drifts. Two implementations of "the same" rule…
Most storage designs assume that whatever is written stays. This record assumes the opposite: keeping bytes is a recurring obligation, and an obligation with no named payer is a bug, not a policy.
A single act at the top of a layered system — one registration, one write, one listing that stays listed — touches a dozen components that each did some work. The easy answer is a central accountant that bills the caller once. That answer…
The easy way to admit a participant is one gate and one credential: pay the price, get a key. The design record refuses that, because a single gate forces a choice between two bad options — cheap enough that anyone can flood in, or…
elsewhere
Each codename is a project. The theme is the class of problem the note is about — the same theme recurs across projects, which is usually the interesting part.