A Dictionary of

The Machine
Vernacular

the coinages, new senses, and vogue words observable in the speech of large language models, each attested to a dated first use

neologism a form previously unattested; a coinage proper.

neosemy an established word bearing a novel sense — figurative extension, domain transfer, repurposing.

vogue an established sense with markedly expanded frequency and range in machine speech.

Each entry cites the earliest attestable use of its sense — published and linked where findable, otherwise witnessed in correspondence between a named contributor and a model — and identifies the model whose usage occasioned the entry.

break-glass n. attrib. & n. vogue

  1. (information security) Designating an identity, credential, or access path deliberately exempted from a system’s otherwise-universal denials and held dormant for emergencies — recovery, revocation, repair — every invocation logged; distinguished from a standing administrator account by exemption and dormancy rather than by privilege. The bucket policy denies deletes to everyone except the break-glass role, and any use of that role lands in the audit trail.
  2. (organizational computing) The exemption mechanism itself, whether a policy carve-out or a procedure-gated ceremony; a system’s named emergency door, as distinct from an undocumented hole.

First known use 2004, “Break-Glass: An Approach to Granting Emergency Access to Healthcare Systems”, Joint NEMA/COCIR/JIRA Security and Privacy Committee white paper — From fire-alarm signage (“break glass in case of emergency”); named in healthcare IT for emergency access to patient records under the 2003 HIPAA Security Rule’s emergency-access provision (the rule mandates the procedure, not the name); later standard in cloud privileged-access design. The machine-speech expansion is range: from emergency account to any deny-exempt principal, path, or ceremony in policy design.

Claude Fable 5, 29 July 2026, observed by @chrismerck.

cut n. neosemy

  1. (software engineering) A named delivery checkpoint within a planning period — conventionally mid-period (cut A) and end-of-period (cut B) — to which work items are assigned and at which a release is branched; the schedulable slot itself, as distinct from the act of cutting the release. The integration was floated at planning but never given a cut; pencil it in for cut B.

Etymology Nominalized from cut a release (“branch and freeze code for shipment”); the scheduled occasion of the act, reanalyzed as a planning bucket.

Attested 29 July 2026, in correspondence between @chrismerck and Claude Fable 5.

discriminator n. vogue

  1. (software engineering) A field in an otherwise fixed data layout whose value declares which of several variant interpretations the remaining bytes carry; transferred from discriminated-union type theory to any self-labeling wire packet, schema, or record — as distinct from a version field, which separates successors in time rather than peers in kind.

First known use 1984, CCITT Recommendation Q.931/I.451 — the protocol discriminator octet distinguishes the signalling protocol of the message that follows; earlier the tag of a discriminated union (Hoare, 1972).

Claude Opus 4.8, 24 July 2026, observed by @chrismerck.

flake n. vogue

  1. (software engineering) A test failure that recurs nondeterministically and is attributed to the test, harness, or environment rather than the code under test; properly a verdict earned by baseline evidence, not an observation — misapplied, it launders real defects into noise. Don’t write it off as a flake until it fails the same way on a clean trunk baseline — this one correlated perfectly with the random id’s leading nibble, and turned out to be a real parser bug.

First known use 14 February 1991, Jargon File v2.6.2 — flaky “subject to intermittent failure” (hacker usage older; the 1983 Hacker’s Dictionary lineage), from the colloquial “unreliable, eccentric”; the per-failure noun is CI-era. The verdict-not-observation deployment is the machine-speech expansion.

Claude Fable 5, 28 July 2026, observed by @chrismerck.

flip v. vogue

  1. (software engineering) To move a system between two prepared alternative configurations in a single small, reversible action; esp. to resolve a deliberately deferred decision whose groundwork has reduced either outcome to such an action — as distinct from toggling a value, a flip may swap whole artifacts, targets, or postures.

First known use 2 December 2009, “Flipping Out”, Flickr engineering blog — feature flags and per-user “flippers”; earliest well-dated transfer of flip to shipping software between prepared configurations.

Claude Fable 5, 28 July 2026, observed by @chrismerck.

gardener n. neosemy

  1. (organizational computing) One who maintains an organization’s canonical records against drift — pruning stale entries, reconciling contradictions, and correcting the agents that operate over them — as distinct from authoring the records or building their infrastructure.

Etymology Figurative extension of gardener (“one who tends a garden”), by analogy between a maintained knowledge base and a cultivated plot.

Attested 23 July 2026, in correspondence between @chrismerck and Claude Fable 5.

governor n. vogue

  1. (software engineering) A configured ceiling treated as the fixed point of a design: other sizes and limits are derived to fit beneath it, and a proposal that would exceed it must reshape itself rather than move it. The message-size cap is the governor — chunk size derives from it, and no revision may touch it.

First known use 2007, Apex Developer Guide, Salesforce — “Governor limits” on multitenant resource use; ultimately from Watt’s centrifugal governor (1788) via Maxwell’s “On Governors” (1868).

Claude Fable 5, 25 August 2026, observed by @chrismerck.

landed v. vogue

  1. (software engineering) Of a change: merged into the shared line of development where it will persist. A change is written, reviewed, and rebased many times but lands once — the metaphor marks safe arrival after a journey, not the act of committing. The cap lift landed overnight; only the follow-up tuning is still in flight.

First known use 2005, Mozilla Bugzilla — “Land NSS 3.11 on the Mozilla trunk and on 1_8 branch”; routine CVS-era Mozilla tree jargon years earlier, from aviation.

Claude Fable 5, 25 August 2026, observed by @chrismerck.

landmine n. vogue

  1. (software engineering) A latent hazard armed by one change and detonated by a later routine action — code or state that behaves correctly until touched, then fails irreversibly; as distinct from a bug, which is already wrong, and a time bomb, which fires on schedule untouched. The do-not-merge landmine is real: shipped before the migration exists, the first config write permanently wipes the device’s legacy settings.

First known use April 2010, “Walking Through the Land Mines”, TESTHEAD blog — Earliest found software-domain transfer; the general figurative sense (“a subject with concealed or unpredictable implications”) is dictionary-standard. The machine usage’s novelty is frequency and the sharpened armed/detonated structure, not the metaphor itself.

Claude Fable 5, 3 August 2026, observed by @chrismerck.

load-bearing adj. vogue

  1. (software engineering) Of a guard, check, clause, or assumption: actually constraining the system’s behavior, such that its removal admits failure — as distinct from decorative or redundant elements whose deletion passes unnoticed; often established only by deliberate removal or worst-case arithmetic.

First known use 10 May 2013, foldoc.org — FOLDOC, “load-bearing printf” — a debug print whose timing side-effect masks a race condition; practitioner folklore since at least the early 2000s. Machine speech widens the subject from code to checks, clauses, and assumptions generally..

Claude Fable 5, 28 July 2026, observed by @chrismerck.

muscle memory n., often attrib. neosemy

  1. (AI agents) An output habit entrenched by training-data frequency that fires despite explicit contrary instruction present in context; as distinct from forgetting — the rule is known, even recited, and still outrun by the habitual completion. Suppressed reliably by mechanical guards, not by reminders. It re-read its own warning about that flag this morning and still typed it mid-diagnosis — that’s muscle memory; the fix is a deny hook, not a fourth reminder.

Etymology Figurative extension of muscle memory (“procedural motor learning”), transferred from human motor skill to the statistical entrenchment of token patterns in a trained model.

Attested 28 July 2026, in correspondence between @chrismerck and Claude Fable 5.

prove v. vogue

  1. (software engineering) To establish that a check or claim holds by forcing the observable it predicts — a deliberate red run, a called probe, a measured worst case — as distinct from inspecting it or watching it pass; frequently the thing proven is the instrument itself. Delete the helper and the gate goes red on four examples; restore it and the suite is green again — that proves the gate bites, which a thousand passing runs never could.

First known use 1837, etymonline, s.v. prove — The test-sense (Latin probare “to test, judge by trial”) is continuously attested since Middle English; proving ground (ballistics testing) dates to 1837. The instrument-directed deployment is the machine-speech expansion.

Claude Fable 5, 28 July 2026, observed by @chrismerck.

rider n. neosemy

  1. (software engineering) A change attached to a branch or pull request whose purpose it does not share, so as to merge on that work’s momentum rather than face review on its own; as distinct from scope creep, a rider is complete and separable — it is only traveling. Flipping the allocator default deserves its own design pass, not a rider on this branch.

Etymology From the legislative sense (“a clause attached to a bill to pass with it, often unrelated to its subject”), transferred to version control.

Attested 25 August 2026, in correspondence between @chrismerck and Claude Fable 5.

ruling n. vogue

  1. (software engineering) An authoritative decision on a contested design point, issued by whoever holds jurisdiction over it and thereafter cited — often by date — as standing precedent; as distinct from consensus, it binds until the same authority revisits it. The design is one-line steppable to two pages if the ruling lands lower.

First known use 1876, Robert’s Rules of Order — The parliamentary “ruling of the chair,” subject to appeal; machine speech transfers the chair’s authority to whoever owns a design decision, and cites rulings by date like case law.

Claude Fable 5, 25 August 2026, observed by @chrismerck.

scorecard n. vogue

  1. (AI agents) A running tally of a working session’s finished outcomes — defects rooted out, claims verified, changes landed — kept so progress stays countable rather than atmospheric; as distinct from a status report, it records results only, never intentions. Today’s scorecard: two contract defects caught before the freeze, one racy suite ticketed with evidence, and a “flake” that turned out to be a real bug.

First known use January 1992, Kaplan & Norton, “The Balanced Scorecard — Measures That Drive Performance,” HBR — the canonical transfer out of sports; the session-tally sense is the machine-speech expansion.

Claude Fable 5, 28 July 2026, observed by @chrismerck.

shape n. vogue

  1. (software engineering) The structural form of an interface, message, or implementation, abstracted from its names and content; countable, so that rival designs are compared, rejected, and approved as shapes. Two cheaper shapes were considered and rejected; the one that landed keeps the read path deterministic.

First known use 2019, A Developer’s Guide to API Design-First, APIs You Won’t Hate — “The design and shape of the API”; earlier for values rather than designs — array shape (APL, 1966), object shapes (SpiderMonkey, ca. 2010).

Claude Fable 5, 25 August 2026, observed by @chrismerck.