emptiness is not correctness
Two defects in the same period, and they share a shape. Both returned success. Neither raised an error. Both produced a surface that simply had nothing on it.
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
the constraint that was never created
A design said orders keep their reference to the area they were priced against. The code agreed. The store did not, and nobody found out for several changes.
isolation belongs to the storage boundary
Serving many independent businesses from one store gives you a choice about where isolation lives. It can live in every query, politely: each read filters for the business it is serving. That works exactly as long as every author, on every…
the ledger is the contract
On a platform shared by many independent businesses, the data shape is not a private implementation detail. Every surface, every workstream and every future feature reads it. So a schema change is a contract change, and the hard part is not…
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.