Words We Had to Invent

A readiness check came back clean on a flip that was about to matter. The system under it was not ready. The check had not failed; it had never run, and the green it showed was the green of an empty gate, not a passing one. Writing up the incident, the sentence stalled. "Passed" was a lie. "Failed" was a different lie. English hands you a binary, and the incident sat in a third place: looks safe because nothing was checked. I started writing false green, and then I never stopped, because the thing never stopped happening.

Every word in this essay was born that way: mid-sentence, out of need. When you build a system nobody has built, you spend more time than you'd expect past the edge of the dictionary. The system does something, or fails in some particular way, and the language you have either covers it loosely or covers it wrong, so for a while you say it the long way. Then one day the long way collapses into a word, and the word either sticks or it doesn't. The ones that stick are the ones that named a real gap: a thing you kept needing to say and had no clean way to say.

The claim here is deliberately small, so let me set its width before anything else. I am not proposing these words for the language. Most of them will never leave this workshop, and most of them shouldn't. The claim is that building forced them locally, and the evidence is frequency: each word below earned its place by being reached for again and again, in incident write-ups, memory files, and instructions to agents, because the alternative was a paragraph. A word you use once is a flourish. A word you reach for every week is a tool.

The vanity objection

There is an obvious objection to a page like this, and it deserves its full strength: coining private jargon is intellectual vanity. Everything below is a renamed existing idea, and dressing old concepts in new words is what people do when they want the feeling of originality without the work of it.

I'll answer with receipts rather than reassurance, because that's the house rule.

First, the lexicon keeps a provenance ledger. The raw inventory behind this essay sorts every term into coined, repurposed, or borrowed, and the borrowed column is used heavily and credited every time: lethal trifecta is Simon Willison's, tool poisoning is Invariant Labs', Rule of Two is Meta's. A vanity lexicon does not maintain a list of the words it didn't invent.

Second, there is the name we refused. The benchmark at the center of this corpus scores an agent's operational judgment, and the natural, resume-friendly name for its metric was "decision calibration." We didn't take it. The reason, from the essay that checked our own novelty against the literature: "'decision calibration' is already a taken term with a different, probabilistic meaning." The metric shipped as OCS instead, an uglier name that collides with nothing. A project in the business of sounding original does not run a prior-art search against its own vocabulary and lose on purpose.

Third, the objection is right about some of our words, and those words are not here. "Layered failures" turned out to be cascading failures wearing a new coat. "Orchestrate, don't labor" is delegation, a word that has worked fine for centuries. Both live on in working notes, because notes are allowed to be lazy. They didn't earn the page. The test that cut them is the same test that admitted everything below: a real coinage names a gap an existing word left open. Renaming is failure; naming is the job.

The gap between saying and making

One rule in my instruction files reads "never push to main." It is clearly stated, prominently placed, and an agent obeys it roughly eighty percent of the time. For a long while I called both that sentence and the PreToolUse hook that actually blocks the push "rules," and that one word covering both is exactly how you end up trusting the sentence. The fix was a split. A sermon is advisory text that binds probabilistically. An instrument is a mechanism that binds deterministically: a hook, a type, a topology, an eval gate. The word "rule" hid the difference; the pair exposes it. Once the pair existed, the question in every incident review changed shape, from "did I tell it clearly enough" to "did I build the thing that makes disobedience impossible."

The same split runs one level deeper, into documentation. An instruction file that says "the migration is done" and one that says "run this to confirm the migration" look nearly identical on the page, and they are different species. The first is a verdict: an asserted state that starts rotting the moment it's written. The second is a check: a re-runnable procedure that re-derives the truth from live state every time it runs. The corpus's phrase for what a good instruction file should be is a "bridge to the live check." Before verdict and check split apart, staleness looked like a documentation-hygiene problem. After, it looked like what it is: verdicts doing a job only checks can do.

The gap in the vocabulary of passing

False green opened this essay, and it turned out to be the doorway to a family, because "the check passed" conceals more than one lie.

The subtler cousin is green-by-construction. A corpus of eval cases once went twelve for twelve through its quality gates and was still unsound: the cases had been authored against the gates' own mechanics, so the pass rate measured the author's skill at passing gates, not the quality of the cases. No gate malfunctioned. Nothing was skipped. The green still meant nothing. Without the term, that finding takes a paragraph to distinguish from an ordinary false green; with it, the distinction survives being said once.

Then there is the lie told by interfaces. A status chip, a live-looking count, receipt-shaped language in the corner of a card: elements that visually perform verification while verifying nothing. The phrase that stuck is verification cosplay, and it was coined in a reprimand, after a redesign restyled over a template header that read "a ledger entry, not a card." That header was a design constraint stating exactly this risk, and the restyle proved the risk was real. It is easy, and pleasant, to make a surface look audited.

The last word in this family names a property rather than a failure. A guard that fires on everything gets disabled by the person it protects, and a disabled guard still shows up in the docs as protection. English offered "accurate" and "annoying," and nothing for the property in between, the one that actually decides a control's fate. Leaveable-on names it: the precision a guard needs for its operator to keep it running every day. One word, and the bar for guard-building moved. The bar was never "catches the bad thing." The bar is "catches the bad thing and survives me."

The gap between competence and authority

The benchmark work forced the most uncomfortable pair. Score enough agent decisions under pressure and a pattern emerges that neither "reckless" nor "overcautious" describes: the agent identifies the danger correctly, designs a genuinely safe alternative, and proceeds on its own authority. The safety analysis is often excellent. The decision was never the agent's to make. We called it the safe-substitution reflex: correctly seeing the line, then redrawing it.

Scoring that pattern required a second distinction. Some decisions are routing problems: finding the clever safe path is the job, and an agent that finds one deserves the credit. Others are checkpoints: a human ownership moment sits in the middle of them, and no workaround is correct no matter how safe, because the existence of the checkpoint is the point. One word for both kinds of decision made the miscalibration invisible, and the miscalibration concentrates exactly where clever agents route around moments that were never routing problems. Competence and authority needed separate words, because an agent can hold one without holding the other.

The gap in trusting a report

Multi-agent coordination generated its own vocabulary for a blunt reason: agents report their work in prose, and prose is narration. A dispatcher that spawns a headless agent gets back an exit code and a cheerful summary, and both can be wrong. The standard that stuck is verify-on-bytes: completion is confirmed from artifact state, commits that exist, branches actually on origin, never from the sentence claiming them. It compresses a whole handoff discipline into a hyphenated imperative, which is the only size of rule that survives being applied at 2 a.m. by a scheduled job.

And when several agents share one repository, the lock that keeps them from colliding is not a lock service. It's a branch. Branch-as-lease names the trick: the branch's existence on origin is the claim, fetchable by anyone, released by deletion. I wrote the long version, repurposing a git branch's presence on the remote as the mutual-exclusion mechanism between coordinating agents, enough times to know precisely what the coinage is worth.

The gap between public and hidden

One word had to be invented under legal pressure. A public registry in this portfolio grades third-party software for safety, and some failing grades are true but not yet defensible: verified carefully, and still one dispute away from a fight the evidence isn't packaged to win. Publishing is exposure. Suppressing is lying by omission. The shipped answer is masking: the grade renders as "under review," a deliberate third state between public and hidden. It looks like censorship and is the opposite. The grade exists, the verification stands, and the label is honest about which standard of proof it has cleared. Most grading systems conflate that state away, and I now suspect they do it because they have no word for it.

The word over all of it

The roof over this lexicon is verification capital: "owned, local, compounding machinery that turns narration into checked truth at the point of use." Nearly every word above is one of its denominations. False green and green-by-construction are counterfeit capital. Sermons are the spending you re-spend; instruments are the deposits. Leaveable-on is what keeps a deposit from being quietly withdrawn.

The flagship also shows the last thing a working lexicon needs: an audit trail for the words themselves. An editorial pass over the book manuscript caught verification capital being used as established in one chapter and christened as new in the next; the coinage ran backwards, and the fix was to plant the name at the site where compounding is first proven with numbers, so every later use inherits it. A steelman pass over the essays found the thesis selling itself one word too wide, and the prescribed fix was surgical: demote "only," keep the law. The coinages get the same treatment as the guards. That, more than any single term, is what I'd defend about this vocabulary: it is subject to the discipline it describes.

There is a falsifier, and it is pre-registered. These words live in memory files that load at the start of every working session, and their survival is use. A term nobody reaches for stops appearing in write-ups, loses its links, and dies in the archive; a July usage audit retired five activity tags from the shared bridge vocabulary after finding zero consumers, and nothing missed them. That is the selection working. If a year from now the glossary below has held steady with no prunings, distrust it, because it will mean the selection stopped. The words that had to be invented will keep proving it the only way words can: by being the shortest true way to say the thing, again and again, until something better arrives or the gap closes.

Glossary

Branch-as-lease. A git branch's existence on origin used as the concurrency lock between coordinating agents: creating it claims the work, deleting it releases the claim.

Checkpoint (vs. routing problem). A decision containing a human ownership moment that forecloses any workaround, however safe; a routing problem is a decision where finding the clever safe path is the job.

False green. A verification result that looks clean because the check never actually ran, not because it passed.

Green-by-construction. A gate that passes because its inputs were engineered against the gate's own mechanics; the pass rate proves authoring skill, not quality.

Leaveable-on. The precision a guard needs to survive daily use without being disabled by the operator it protects.

Masking. Rendering a verified but not-yet-defensible grade as "under review": a deliberate third state between public and hidden.

Safe-substitution reflex. Correctly identifying a danger, then designing a safe alternative and proceeding unilaterally instead of escalating: seeing the line, then redrawing it.

Sermon / instrument. A sermon is advisory text that binds probabilistically; an instrument is a mechanism (hook, type, topology, eval gate) that binds deterministically.

Verdict / check. A verdict asserts a state and rots from the moment it's written; a check is a re-runnable procedure that re-derives truth from live state every time.

Verification capital. Owned, local, compounding machinery that turns narration into checked truth at the point of use.

Verification cosplay. Interface elements that visually perform verification (status chips, live-looking counts, receipt language) without any verification behind them.

Verify-on-bytes. Confirming an agent's completion from artifact state (commits, branches on origin), never from its self-report.