MERIDIAN

24 notes filed under MERIDIAN, newest first. Same rules as the rest of the pile: a codename, a theme, and no internals.

codename MERIDIAN · 24 notes · 24 themes · all codenames

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

MERIDIAN · open problems · 2 min read

the anchor it drew itself, and said so

A catalog cannot prove itself. Whatever sits at the root of authority has to be named, and the honest options are to name something external — which this design cannot supply — or to name itself, which is a statement about bootstrapping…

read

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.

ABACUS 60 FLINT 12 KEEL 24 LARDER 24 LATTICE 36 MERIDIAN 24 MISE 24 SCRIBE 12 TROUPE 12 UMBRA 24 browse 244 themes

MERIDIAN

MERIDIAN notes

the anchor it drew itself, and said so

Other codenames