Command Explorer › scale: — the reply's measure › wordy
scale:wordy
The long version, fully aired out — expansive on what's known, with the effort capped: no deep dive, no rabbit holes.
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.What it does
The complete, unhurried long version of what is established — brief's antonym on length, with the effort explicitly capped: no escalation into fresh deep research or analysis to fill the length, and no rabbit holes. It clashes with scale:deep on effort and with scale:brief and scale:executive on length — last one wins.
The registry's own words: The long version, fully aired out — expansive on what's known, with the effort capped: no deep dive, no rabbit holes.
Fire it — usage examples
Tell me everything about how the move day will go.
→ scale:wordy
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is reply wordy. Dictated directives fire deliberately, never by accident.
What the agent actually does
Airs out what is established — it does not escalate into fresh deep research or analysis to fill the length. If the material runs out, the reply ends rather than padding.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-scale-wordy ↗.
When the host can't
No host capability required. Length is filled from what is established; where little is established, the reply is as long as the material honestly supports — say so rather than padding or inventing.
Conformance — “done when”
Everything that's known is on the table, in full — and nothing new was dug up to pad it.
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.