v0.6 Draft
Normative

The loop, on one page

What to say, without the reasoning. The specification explains why; this is the part you put on the wall.

Print this. The full specification explains why; this is what to say.


The four beats

1. Call. Say the kind of task and stop. Everyone who could own it says "Ready." Only then describe it.

2. Claim. One person says it back in their own words and takes it: "Heard — <what you understood>. <Name>, on it."

3. Co-prompt. Say the prompt out loud before you send it: "Prompting now: …" Anyone adding something says "Adder", you say "Go ahead", and they say it into your agent themselves. Then "Finished."

4. Close. The agent works while the meeting carries on. You report back with "Preliminary: …", then close it: "Good" / "No good" / "Parked — waiting on …" / "Dropped — covered by …"

Anyone, at any time: "Status." Every owner with something open answers "<Name> reporting …"


Every phrase

SayWhen
ReadyYou have stopped and the caller may describe it.
HeardYou registered the call but need a moment — then say Ready. Also leads a restatement.
Clarify: …Asking a question. Asking is not claiming.
On itYou are taking it. Say your name with it.
Already mineYou own it from earlier. Give status instead.
PassTwo of you claimed. You are standing down.
Prompting nowYou are about to say the prompt aloud. The room holds new calls.
AdderYou want to add to someone's prompt.
Go aheadYou are handing them the floor to say it into your agent.
Not adding — …You are refusing an addition, with a reason. Cost counts as a reason.
FinishedYour prompt is done. The floor is free.
HoldYou have something queued but they are mid-prompt.
Files firstAttach the drawings before prompting.
I propose …Floating an approach before prompting.
Add: …Offering context without taking the floor.
YoursHanding the task to another discipline.
RunningThe agent is working.
Back with …You have a result.
PreliminaryNobody may rely on this yet.
Check: …Asking the caller to try it.
Working / Still brokenThe caller's answer to a check.
Good / No goodAccepted. Rejected.
Parked — waiting on …Blocked. Name the blocker and who clears it.
Dropped — covered by …Overtaken. Name what covers it.
Out of scopeThis is outside the engagement.
StatusAnyone, any time: what is everyone running?
… reportingYour answer to a status call.

Three rules that matter more than the words

Do not describe until everyone has said Ready. Half a room reading email is the failure this prevents.

Say the prompt out loud. Not "I'm on it" — the actual prompt. It is the only moment the room can catch a misunderstanding while it is still cheap.

Every task you claim gets an ending, out loud. Good, No good, Parked, or Dropped. A task nobody closed is indistinguishable from one nobody did.


Shortcuts

Straight to one person: say their name first — "Midhun — code. Is a damper required there?" No one else has to acknowledge.

Someone in the room who does not know any of this: put their question into the loop for them, and check you got it right — "Decision — Mark is asking how we landed on the DOAS. Prompting now: … Mark, does that sound right?"

Say it however you say it. Any call word works with "question", "study", or "analysis" on the end. "Code question" and "code" are the same call.