retention that names a payer or loses the thing
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.
field notes codename
MERIDIAN
24 notes filed under MERIDIAN, newest first. Same rules as the rest of the pile: a codename, a theme, and no internals.
MERIDIAN notes
all themes
admission 1
archival 1
artifact identity 1
authority resolution 1
behaviour model 1
compatibility 1
delegated authority 1
economic mechanism 1
evolution 1
executable specifications 1
fork mechanics 1
founding identity 1
migration 1
normative record 1
open problems 1
record discipline 1
recursive structure 1
relationship model 1
retention 1
scope discipline 1
settlement 1
state bounds 1
supersession 1
unit independence 1
elsewhere
Other codenames
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.