Nobody was listening when the constraint was given
The same kind of coordination meeting, run the way most rooms already run. Nothing here looks like a failure while it is happening — which is the point.
- Owner's representative
- Routing — quick one. The tenant wants the walk-in cooler moved to the north wall, so the refrigerant lines have to come from somewhere else.
Routing - Architect
- Listening.
acknowledge - (the MEP engineer is on mute, mid-sentence with someone off-camera)
- Owner's representative
- And the structural drawings show a beam right where the old route was, so it can't just go back the way it came.
- MEP engineer
- Sorry, back — yes, I'll look at the cooler.
claim - MEP engineer
- Prompting: find a refrigerant line route from the condensing units to a walk-in cooler on the north wall.
prompting - Architect
- Add — remember the beam.
augment - (the MEP engineer is reading the agent's output and does not respond)
- MEP engineer
- Route works. Straight shot down the corridor.
- Owner's representative
- Great, I'll tell the tenant it's fine.
Breaks: Acknowledged attention
Breaks: Restatement on claim
Breaks: Acknowledged augmentation
Breaks: Explicit disposition
The room believed it had answered the question. It had not. Three rules were broken in under a minute, none of them noticeably, and the result left the room as a commitment to a tenant. Every one of these failures is invisible in the moment and expensive later — which is the entire argument for saying the words out loud.
What it cost
Every one of these is invisible in the moment and expensive later, which is the whole argument for saying the words out loud.
Acknowledged attention
turn 4The Caller MUST NOT DESCRIBE until every Listener has acknowledged.
The owner's representative described the task while the MEP engineer was off the call. The beam — the single fact that decides the answer — was stated to a room where the only person who could act on it was not listening. Waiting for the second acknowledgement would have cost four seconds.
Restatement on claim
turn 5A CLAIM MUST include a restatement of the task.
"I'll look at the cooler" is agreement, not a restatement. Had the engineer said the task back in his own words, he would have discovered on the spot that he had missed the constraint, and the room would have heard it too. The restatement is the cheapest error-detection in the loop, and it is the first thing rooms drop.
Acknowledged augmentation
turn 8The Owner MUST state aloud, for each augmentation, whether it was incorporated.
The architect supplied the beam a second time and got silence. She reasonably assumed it had been included. It had not — the prompt had already run without it. Two words, "Not in", would have caught the whole thing; the agent's answer was correct for the question it was actually asked.
Explicit disposition
turn 9Every claimed task MUST reach exactly one terminal state, stated audibly.
"Route works" is a status report, not a disposition. Nobody in the room could say afterwards whether the task had been closed or was still open, and the owner's representative treated it as settled. One word — "Good" — would have made the close audible and reviewable.