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 · delegated authority · 2 min read

delegation that keeps the terms private and the settlement public

Delegation is where most systems quietly become custodial. You grant someone authority to act for you, and the record of that grant ends up in whatever store the delegate controls. You find out how it was used afterwards, if at all.

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

delegation that keeps the terms private and the settlement public

Other codenames