Exchange types
The model assigns each message one of these types.
| Type | Example messages | Ceiling |
|---|---|---|
factual-question |
“Is the new endpoint deployed?” “Where is the retry limit set?” |
150 words |
status-and-resume |
“Where are we?” “Let’s continue.” “The PR merged.” |
250 |
approval |
“Q1 a” “Go ahead.” “Go ahead, but skip the migration for now.” |
250 |
thinking-out-loud |
“Let’s talk through the caching options.” “Does this plan make sense?” “Can we run this in CI instead?” |
350 |
diagnosis |
“Why does the build fail on Windows?” “Is this a good way to handle retries?” |
500 |
redirect |
“Use the existing helper instead.” “I removed that file on purpose.” |
250 |
broken-report |
“The test still fails.” “I get 7 results, not 5.” |
250 |
work-request |
“Add a test for the parser.” “Open a PR with both fixes.” |
400 |
canned-review |
A review prompt that a script sends | 300 |
harness-probe |
“Answer in one line.” “Reply with only the token.” |
The requested form, else 40 |
default |
A greeting, a pasted fragment, or a mix of three or more types | 250 |
Ceilings count everything you read, coded items included.
When your message lists items, every item on it gets a line, whatever the ceiling.
Each type’s cues, shape, and examples are in styles/.