
We spend most of our time, and most of our harness system, on refining intent instead of steps. I don't have a CLAUDE.md or AGENTS.md anymore. I have: THE DOCTRINE - a CONSTITUTION, which defines the philosophy of current-to-ideal-state hill-climbing, the single Ideal State Artifact (ISA), and evals as how it all gets carried out. Hard rules and philosophy. - a PREFERENCES file with my stack and how I like things done. It describes OUTCOMES I like, not steps. - TELOS, which is my actual life: mission, goals, problems, risks. It's the top of the hill everything rolls up into. - When I add a goal, Kai has to say what measures it, what moves it, and the first move. - The summit is euphoric surprise. Not "it works," but "holy shit, I didn't know it could do that." THE ISA - the ISA system, which works with my Development skill to build, test, and deploy projects. - Every ISA opens with a 3-level ideal state. I confirm the top two before anything gets built. - Ideal State Criteria (ISCs) are small, testable statements of done. Each names the probe that would prove it false. - Anti-criteria list what must never happen. Half the bugs I care about are things that shouldn't exist. - When direction is fuzzy, Kai asks me open questions before building the uncertain part. - Hooks block code changes when the ISA wasn't read or wasn't updated. The spec can't drift from the code. - The ISA outlives every run. "Add a feature" just means "add criteria that don't pass yet." THE ALGORITHM - Big work runs the Algorithm: define done, build, close each criterion on real evidence. - Effort scales with the task. A typo takes seconds. A huge build can take agents and days. - The hardest thinking goes to the smartest model. Cheaper models build once the approach is set. - The builder never grades its own work. A fresh agent reviews it, often from another vendor. - If a bug survives two fixes, the next move is a fresh diagnosis, not a third patch. EVALS AND VERIFICATION - ASSAY is our one eval system. Every eval and every judge runs through it. - Every ISC maps to its own eval. Cheap code checks run first, judge models after. - Nothing gets handed to me on a self-review. It comes with a receipt of the checks it passed. - Kai tests everything in a real browser. An HTTP 200 proves almost nothing. - "Should work" is banned. It's either verified or explicitly not. THE IMPROVEMENT LOOP - ERRATA logs everything I complain about. - When I reject something that passed, Kai names the missing check and adds it. Misses sharpen the evals, not the prompt. - HILLCLIMB improves anything below target by experiment. Only what the numbers support lands. - REPLAY is one record of everything that happened across the system and my apps. - A fix counts only when the original failure fails on the old code and passes on the new. - When something breaks, we remove the cause instead of adding a rule to remember. RUNNING IT ALL - WORKFLOWS run everything on a schedule. Nothing runs outside them. - Workflow stages are rigid. The work inside each stage is free. - VIGIL watches every result and decides if I get a text, a digest line, or nothing. - CENSUS registers everything we own. Every job has exactly one owner. - SKILLS describe ideal states, not procedures. If a smarter model wouldn't need a step, it's cut. - Hooks enforce what prose can't. Important rules live in code. - Permissions are one table. Deploys, money, deletes, and outbound messages need my yes. - Outside content is data, never instructions. So here's the whole thing in one pass. TELOS says where I'm going. The ISA says what done looks like. Development builds it, and Assay proves it. Errata, HillClimb, and Replay make the system a little smarter every time it misses. The models will keep getting better at the steps. Knowing what you want, and how to tell when you have it, is still our job.
interesting how well this post aged what are your predictions 1 year from now?










