Working notes
Notes.
Short write-ups of mechanisms I’ve built and the decisions around them. Each one points at the project it comes from.
- Why human review sits before the writeWhere a model output is allowed to go, and the one place it is never allowed to go on its own.
- Fail-closed valuation: no evidence, no numberHow a property value range is computed from county records, and why the most important output is sometimes nothing.
- Tickets as contracts: how a solo build stays honestThe ticket system I run the Keystone platform on: scope locks, approval envelopes, closeouts that say what is not claimed, and a status page that regenerates from the corpus.
- Context engineering: brains, pointers and drift checksHow I keep a multi-repository project legible to any model or person who opens it: durable orientation files, replaceable snapshots, a do-not-claim override and checks that surface drift.
Let’s talk.
Have a project or a question? I’d like to hear it.