codalume.com

field notes codename

ABACUS

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

codename ABACUS · 60 notes · 58 themes · all codenames
all themes data-legitimacy 2 reproducibility 2 adapter archaeology 1 audit finding 1 audit methodology 1 calendar-defect 1 caveat-retraction 1 comparison-precision 1 confound 1 correction discipline 1 correction-discipline 1 cost-model verification 1 data legitimacy 1 data-provenance 1 defect class 1 delegation-postmortem 1 documentation-accuracy 1 effect-containment 1 environment-identity 1 equivalence-oracle 1 fail-closed gating 1 failure-suppression 1 filter-validity 1 gate-calibration 1 history-hygiene 1 identifier-keying 1 implementation-parity 1 instrument-validity 1 integration-verification 1 irreversibility-control 1 kill-switch 1 latency diagnosis 1 liveness-detection 1 look-ahead-control 1 measurement-guard 1 multiplicity 1 negative-control-testing 1 operator-gate 1 pre-registration 1 programme-closure 1 protection-atomicity 1 record-integrity 1 reproduction 1 response-reconciliation 1 restart resilience 1 restart-engineering 1 result-withdrawal 1 reversal 1 reversibility 1 review-retraction 1 risk-decomposition 1 safety-margin 1 schema-fidelity 1 search-boundary 1 selection-instability 1 silence-as-evidence 1 specification-divergence 1 state-reconciliation 1
ABACUS · reproduction · 2 min read

the same answer on a different machine

A large sweep produced a map of candidate configurations, and the map was produced once, on one machine, by one program. That is exactly the situation in which a subtle dependency on the machine — an ordering, a threading choice, a…

ABACUS reproduction
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