Meap

Written with Claude. The sentinel that existed to remember what the system forgot The clearest example of a ghost-guard (a check that protects against a condition that no longer exists, or never should have) I’ve found is one the field-assessment platform created for itself. On every re-cost pass, the cost agent (the automated step that recalculates repair costs) re-emits an engineer’s years override under its own author tag. That one round-trip erases the human-authored signal from the append-only event log (a tamper-evident journal of every change, keyed by author and timestamp). The system then stamps a sentinel flag called _years_auto (a presence marker the gateway reads to infer ownership), so it can later infer whether an engineer or the agent wrote the value, because the round-trip already destroyed that information. ...

Written with Claude. The governor issue closed mid-session At 16:52 UTC on May 22, meap2-it issue #1352 (“No Syncthing reads at runtime on dev-pi”) closed. That was the cascade governor: the issue that couldn’t close until every leaf under it had closed. Three concurrent Claude sessions across three repos for one focused day got it there. One session couldn’t have done this work at any speed. The cascade structure (a named invariant at the top, leaves underneath, each leaf owned by whichever repo holds the bytes) is what made parallel finishing possible. Some cross-cutting architectural debt isn’t single-session work; the cascade is the shape that admits parallel work closing it at all. ...

Written with Claude. Claude Said SQLite Would Work Fine, and I Pushed Back This has happened more than once. A storage problem comes up during MEAP’s development (sync conflicts, history, recovery) and the suggestion arrives: use a database. SQLite is the usual recommendation. It’s the right answer for most teams, and it’s the first tool in the context window for good reason. ...

Written with Claude. The field visit, the data analysis, the issue filing, and this blog post were all done in one session. The Core Problem The worst thing an AI pipeline can do is put a plausible falsehood in a delivered report that nobody catches. Not a typo. Not a formatting issue. A statement that reads like a field observation, passes review because it sounds right, and lands in front of a client as fact. ...

Inspired by All You Need Is Kill by Hiroshi Sakurazaka—a story about a soldier trapped in a time loop who uses each death to get better at surviving. Part 1: The Death The war is already happening. Has been for decades. The battlefield is commercial real estate. Office towers, hotels, warehouses, medical buildings. Every one of them hiding secrets. ...

I built Memory Bank for my home infrastructure repo. Three months later, I finally applied it to the system that actually makes money. Then during a real project, the whole data architecture changed.