contract changes arrive as reviewed changes
A written contract and a shipped implementation drift apart in one direction: the implementation wins and the document becomes archaeology. Two practices in this period worked against that.
field notes codename
MISE
24 notes filed under MISE, newest first. Same rules as the rest of the pile: a codename, a theme, and no internals.
MISE notes
all themes
artifact-verification 1
blast-radius 1
commit-ordered-state 1
contract-change-review 1
declared-versus-enforced 1
evidence-honesty 1
failure-visibility 1
first-visit-mounting 1
generated-desired-state 1
harness-fidelity 1
history-hygiene 1
migration-rehearsal 1
onboarding-consent 1
operational-fallback 1
permission-resolution 1
registration-versus-deployment 1
repeatable-ingestion 1
request-correlation 1
shared-data-model 1
tenant-isolation 1
test-isolation 1
theme-only-tenancy 1
translation-completeness 1
unconfigured-versus-out-of-area 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.