Thinking, written down
Notes from building — the decisions, the dead ends, the things I’d do again. The hub owns the depth; a few pieces cross-post to Medium.
7 pieces
Aug 2026 · medium ↗The second memoryI gave a real project a second kind of memory, a code graph from Graphify that maps what actually connects to what, sitting under the context system I write by hand. The one I write holds the why. The one the code writes back holds the what is. The gap between them is where the bugs live.methodologyaitools→Jul 2026Stop prompting your AI. Start conducting it.One command that runs my whole build pipeline. It reads where the project stands, recommends the next slice, runs the right step, and hands control back at every real checkpoint. This is build-flow, a skill I built: the conductor I put in front of the method.methodologybuild-flowworkflow→Jul 2026Building with AI: my methodologyHow I actually build software with AI, learned before AI and adopted on purpose. This is the map: a memory that lives outside the chat, a paper start, a loop that lets an agent build for hours without drifting, and the handful of tools that run it.methodologyaiworkflow→Jul 2026A memory that outlives the chatThe set of plain files that give a project a memory outside the chat, so an agent starts every session already knowing what was decided. This is context-system, a skill I built: a foundation that wins, a build graph, a progress log, and the one file I add only when security is the point.methodologycontext-systemworkflow→Jul 2026Design, build, proveThe three steps in the middle of every slice, done by three skills I adopted from JS Mastery Pro. architect settles the decision in a spec, develop builds only what was designed, and check proves it by running the real thing. Not everything in my toolbox is mine, and that is the point.methodologyworkflowtools→Jul 2026A context system for a security projectThe same build method, taken into a project whose whole job is security. A second layer of docs, one home for every fact, a few honesty rules, and a system that caught its own drift.methodologysecuritycontext-system→Jun 2026Start with what must never happenHow VolleyPacket keeps one customer's data away from another's, and why every rule is written as a thing that must never be true instead of a thing the system should do.isolationsecurityarchitecture→