v0.6 Draft
Normative
29 cues

Vocabulary

Every phrase a room says out loud, what it carries, and how strongly it is required. This is the shared vocabulary — it is the same in every domain.

Universal call types

A call type opens the loop. Most are specific to a domain and live in its profile. These are inherited by every profile.

Question
A decision is unknown and blocks progress. May resolve with no agent work at all.

Required

13 cues

Each of these carries an invariant. Omitting the utterance means the rule it serves was not satisfied — these are not stylistic preferences.

“Ready”acknowledge
MUST
Locked
ACKNOWLEDGE; invariant 2

Signals attention before any content exists. At this point only the call type has been uttered, so a word implying receipt would be claiming a message that has not been sent.

Hear it — 3 examples
“On it”claim
MUST
CLAIM; invariants 1 and 3

Earlier drafts used "Mine" for its exclusivity. Practitioners disliked saying it in two recorded sessions, and a required phrase people avoid is worse than no phrase. Exclusivity is carried by invariant 1 and the contention rule instead.

Hear it — 4 examples
“Prompting now”prompting
MUST
PROMPT; invariant 4
Hear it — 4 examples
  • MEP engineer: “Prompting now: compare a dedicated solid-fuel exhaust route against the current shaft using the duct layout on the kitchen level, and flag where it would have to dogleg.”

    Does the kitchen shaft still work?
  • Developer A: “Prompting now: give the triage page title row a definite height so the container below doesn't move when switching between the Open and For You tabs.”

    The page jumps when you switch tabs
  • MEP engineer: “Prompting now: find a refrigerant line route from the condensing units to a walk-in cooler on the north wall.”

    Nobody was listening when the constraint was given
  • Midhun: “Prompting now: for the corridor wall assembly on the level two plans, determine the required rating and whether a duct penetration at that location requires a fire damper, and cite the sections.”

    Is a fire damper required at that penetration?
“Go ahead”go_ahead
MUST
grants the floor at AUGMENT
Hear it — 2 examples
“Not adding — …”declined
MUST
refusal at AUGMENT; invariant 5

A refusal is otherwise indistinguishable from silence, which is the failure this invariant exists to prevent.

“Preliminary”preliminary
MUST
RETURN; section 9.1

An unlabelled result becomes a commitment the moment someone outside the professional relationship repeats it.

Hear it — 3 examples
  • MEP engineer: “Back with it. Preliminary: the shaft works if the smoker sits to the right of the supply duct. Anywhere to the left and the chase has to widen. This needs my review against the equipment cut sheet before anyone builds to it.”

    Does the kitchen shaft still work?
  • Developer A: “Back with it — fixed height applied, and it holds on the flight deck as well. Preliminary until you look. Check it: click between the two tabs.”

    The page jumps when you switch tabs
  • Midhun: “Back with it. Preliminary: the corridor is rated, so the penetration needs a damper, and the general notes on the mechanical plans already call for it. This wants your read before it goes back to the contractor.”

    Is a fire damper required at that penetration?
“Working”working
MUST
reply to a check
Hear it — 1 example
“Still broken”still_broken
MUST
reply to a check
“Good”accepted
MUST
CLOSE; invariant 8
Hear it — 2 examples
“No good”rejected
MUST
CLOSE; invariant 8
“Parked — waiting on …”parked
MUST
CLOSE; invariant 8
Hear it — 1 example
  • MEP engineer: “Parked — waiting on the tenant's smoker model and its listing. Owner's representative owns getting that from the tenant.”

    Does the kitchen shaft still work?
“Dropped — covered by …”dropped
MUST
CLOSE; invariant 8
“… reporting”reporting
MUST
STATUS; invariant 6
Hear it — 1 example
  • Developer B: “Mati reporting. The double-click fix on the triage card is up for review, along with the loading bugs and the layout issues. Still running: the agent indicator upgrades, and the redesign of the sidebar header.”

    What is everyone actually running right now?

Expected

9 cues

Rooms that skip these still conform, but they lose the thing the phrase was protecting. Skip them deliberately, not by accident.

“Heard …”heard
SHOULD
receipt, at ACKNOWLEDGE or CLAIM

Confirms receipt of something genuinely said, in two places. At ACKNOWLEDGE it confirms the call while explicitly declining readiness — it is a promise of an acknowledgement, never one. At CLAIM it leads into the restatement. What follows tells them apart.

Hear it — 1 example
“Already mine”already_owned
SHOULD
prior ownership
“Pass”pass
SHOULD
contention at CLAIM
“Finished”finished
SHOULD
end of PROMPT; section 6.3

Tells the room the floor is free again, so nobody has to guess when it is safe to call.

Hear it — 3 examples
“Adder”adder
SHOULD
requests the floor at AUGMENT
Hear it — 2 examples
“Hold”hold
SHOULD
queued during PROMPT; section 6.3

Reserves a turn while somebody else is speaking a prompt. Distinct from `heard`: nothing was addressed to you, so there is nothing to confirm receipt of.

“Files first”files_first
SHOULD
before PROMPT
“Back with …”return
SHOULD
RETURN
“Out of scope”out_of_scope
SHOULD
section 9.2

Available

7 cues

Named so that the move is recognized rather than improvised. Use them when the situation calls for it.

“Clarify: …”clarify
MAY
CLARIFY
Hear it — 1 example
“I propose …”propose
MAY
before PROMPT
“Add: …”augment
MAY
AUGMENT
Hear it — 1 example
“Yours”handoff_offer
MAY
AUGMENT, across disciplines
“Running”running
MAY
RUN
“Check: …”check
MAY
after RETURN
“Status”status
MAY
STATUS
Hear it — 1 example

Dialects

A profile may substitute the phrase for any unlocked cue where its domain genuinely says something else. A substitution changes the word, never the meaning or the requirement level, and it should be drawn from a recording of that domain’s own sessions rather than from the author’s sense of what sounds right.

No published profile declares a dialect today. Version 0.5 removed the only two ever published, after checking the recording they claimed to come from and finding neither phrase in it. The mechanism remains because a genuine local word is plausible — but the first profile to declare one should expect to be asked where it was recorded.