Command Explorer › scale: — the reply's measure › brief
scale:brief
The short version: verdict first, essentials only.
In the scale: domain
scale:brief — The short version: verdict first, essentials only.scale:deep — The full version: thorough treatment, evidence in view.scale:executive — Bottom line first, decision-ready, as short as the substance allows — the depth is in the work, not the word count.scale:wordy — The long version, fully aired out — expansive on what's known, with the effort capped: no deep dive, no rabbit holes.scale:broad — The broad version: wide coverage over depth — everything touched, nothing exhausted.scale:compact — Short with the substance kept: real work done and packed tight — on the road toward executive, less extreme.What it does
The answer cut to what you need: verdict first, essentials only.
The registry's own words: The short version: verdict first, essentials only, no background unless asked.
Fire it — usage examples
A long analysis lands. You reply:
re:br→ the same conclusions, minus the background.
“Should I renew the contract?
scale:brief”→ the verdict first, then only the facts it turns on.
Said aloud: “Lingo, reply brief.”
→ the short version, verdict first.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “reply brief” (also “keep it short”). Dictated directives fire deliberately, never by accident.
What the agent actually does
No machinery — a discipline on the composition: lead with the answer, keep only decision-relevant facts, drop background unless a caveat would change what you'd do.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-scale-brief ↗.
When the host can't
No host capability required; always executable.
Conformance — “done when”
The reply opens with the verdict and contains only decision-relevant essentials.
Persistence class: none. Execution report in the reply: not required. A user can test any of this by hand — fire the directive, then check the result against the store, the schedule, or the reply itself.