Code, System One, System Two and a person: which model you keep, and which you can replace.
Robert Blust · Software Engineer & Architect
Two of them are models that learned. Three of them are files you keep.
Each decision goes to the lowest layer that can make it.
The vocabulary, and the rules for writing each page, in Markdown, at a release an instance pins.
A company’s facts as Markdown in git, checked against the release it adopted. No tool and no model owns it.
References, schemas, ids. The same answer every run, and no model asked.
Each writing rule becomes a typed question. Jev answers with a choice and a probability. The owner says yes to exactly what leaves the machine.
It advises, and changes nothing.
Skills draft. Validate reads the judge’s flags first, then every page. The server and the chat answer, and name what each answer rests on.
A pass that finds nothing approves nothing. The Owner’s word merges.
Each step does what it is good at, and says what it leaves to the next.
What stays is what you wrote. What changes is what reads it, and each says whether it is replaceable today or by design.
Every model is pinned. A new one is measured against the same company before it is named.
The model you will change most often is the one you should depend on least.
Then the next model is a pin you move, not a project you start.