Tagged acceptance
3 pieces
- · 10 min read
The Balance Behind Every Screen: Thirteen Modules of Leave Screens Are One Arithmetic Identity
An entitlement system written up as thirteen modules of screens has one real deliverable, and it is an arithmetic identity: allocated, less used, less pending, equals available. That identity has to stay correct through cancellations after a calendar change, double submissions, administrative adjustments and year-end resets. A click-through acceptance checklist exercises none of those, which is how these systems pass acceptance and then produce balances nobody can defend.
- · 10 min read
Accept The Work, Not The Claim: An Agent's Own Status Is Not Evidence
A headless agent run that hits a rate limit can exit with a success status and a zero exit code, having written nothing at all. Every reliability feature that reads the agent's own account of what happened, retry, recovery, the status pane, then repeats that false claim instead of catching it. The only fix is an independent check between running and accepting.
- · 10 min read
Six Drills That Break An Agent: Accept Milestones By Breaking Them, Not By Demonstration
A demonstration shows an agent pipeline working on the path its author chose. A drill breaks it on purpose and records what the system does. Six drills cover most of what goes wrong: killing the worker mid-run, hitting the output token cap, resuming and watching the budget, cancelling a run that does not heartbeat, rate-limiting mid-run, and changing the workspace through the shell behind the tool's back.