Development record

abcd records how each preflight on a machine behaved

intentdraftsminoritd-2610262140595217

Press Release

abcd keeps a record of how each preflight on a machine behaved: how long it waited for its turn and how long it ran, the CPU its whole run used, whether a test timed out, and how busy the machine was with other people's work at the time. The record is the person's own, kept on their machine under abcd's home, bounded in size and the same shape on macOS and Linux, and they can read it through one command. It is the evidence any later tuning of the machine's settings rests on, and the first case of the wider record of what abcd costs to run.

Why This Matters

Why this matters to the user — replace before planning.

Mechanism

Prompted (the claim-recording gradient): why the authors expect this to work, as a falsifiable "we expect X because Y" — not the outcome restated. Replace this line with the claim, or with the exact token None stated. alone on its line to record the claim as considered and declined.

Scope Conditions

Required (the claim-recording gradient): the population, platform, scale, or assumptions this claim holds under, one per top-level bullet — abcd intent plan stamps each with a persistent identity. Replace this line with those bullets, or with the exact token None stated. alone on its line.

Acceptance Criteria

Required (the itd-1 discipline): add at least one Given-When-Then bullet describing the verifiable bar for "shipped" before this draft can be planned.

Open Questions

None recorded yet.

Audit Notes

Empty. Populated by intent-auditor when intent moves to shipped/.

Frontmatter

id	itd-2610262140595217
type	intent
lifecycle	drafts
severity	minor

.abcd/development/intents/drafts/itd-2610262140595217-abcd-keeps-a-record-of-how-each.md
open on GitHub ↗ · commit history ↗

References2

itd-2610262127138979A preflight waits for its turn as one whole runblocked by
itd-2610262127138979A preflight waits for its turn as one whole runbuilds on

Referenced by3

itd-2610262141001890abcd adjusts how many preflights run at once from what it recordedblocks
itd-2610262141001890abcd adjusts how many preflights run at once from what it recordedbuilt on by
itd-2611011325403127Every landing shows what it cost and the next run's estimatebuilt on by

mentions7

dcn-26110120490462592026-11-01 — With the drain wound down on 2026-11-01, three streams of work start in parallel: the terminal drain (itd-2610222215485265) in this session, the load work (itd-2610262140595217, itd-2610262141001890 and the memory floor) with Eve, and the CI work (itd-2610261025516272 and its new drafts) with Henry. While the subscription's weekly budget is near its limit, every agent a build or drain hands out runs on the person's API key through the claude runner, never as a host subagent; only the driving sessions stay on the subscription.
iss-2611011402496418A planning interview run in a plain terminal on the API-key runner ended at its first question on 2026-11-01. The interviewer wrote a sound question, but abcd's question check refused it at 39 rows against a 32-row limit, and the refusal was treated as the runner's invalid answer: with no host fallback in a terminal the interview stopped, printing 'runner: claude invalid for planning-interviewer ... the contract's validator refused its answer: the question breaks 1 rule(s): tab 1, whole tab (rows)'. The person was left with an internal message and no next step. The brief tells the role 'abcd refuses a receipt ... whose question breaks a rule below, and the interview stops', and only a refused done outcome is ever handed back for another turn. A host session's own question check shows an over-long question with a warning and has the agent redraft refused ones silently, so the terminal route is stricter than the host route for the one rule a model cannot count exactly. The product thinker ruled the same day (dcn-2611011402510346) that an interview must never stop on a question abcd's check refuses, and that anything which does end an interview tells the person in plain words what happened and what to do.
itd-1Every Intent Has Acceptance Criteria; Every Audit Verifies Them
itd-2611011325421304A one-package change is checked in minutes, not the whole suite
itd-2611012048006057abcd's load gate waits for memory as it waits for load
spc-2610262202438999A preflight waits for its turn as one whole run
spc-2611020732419632abcd's load gate waits for memory as it waits for load