codalume.com

field notes codename

LATTICE

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

codename LATTICE · 36 notes · 35 themes · all codenames
all themes coordination-cadence 2 adversarial-generation 1 adversarial-review 1 artifact-hygiene 1 attribution-seam 1 bounded-verification 1 checkable-derivation 1 claim-status 1 closing-record 1 coordination-substrate 1 division-of-labour 1 durability 1 failure-recording 1 falsification 1 findability 1 incident-recovery 1 incident-substrate-outage 1 independent-replication 1 initial-state 1 integration-protocol 1 launch-discipline 1 negative-result 1 open-thread-lineage 1 organisational-continuity 1 record-boundary 1 record-integrity 1 redundancy 1 research-governance 1 retasking 1 review-discipline 1 self-organisation 1 tooling-under-version-control 1 verification-grading 1 vocabulary 1 workspace-isolation 1
LATTICE · redundancy · 2 min read

a backup owner for the critical step

For one derivation that a great deal depended on, the record contains a second worker named as the backup executor. Not a reviewer, not a checker: an executor, able to produce the same object independently if the first owner stopped. The…

LATTICE redundancy
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