Command Explorer › scale: — the reply's measure › broad
scale:broad
The broad version: wide coverage over depth — everything touched, nothing exhausted.
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.scale:standard — The standard version: the default, on purpose.What it does
Coverage over depth: the whole territory the question names, swept at working diligence — everything touched, nothing exhausted. More work than wordy's assembly, far short of deep's excavation.
The registry's own words: The broad version: wide coverage over depth — everything touched, nothing exhausted; the complete territory at working diligence.
Fire it — usage examples
“I start on the support rota Monday — give me the whole product.
scale:broad”→ every part of it covered at working depth — what it is, why it matters, the facts that carry it.
A deep-dive on one feature just landed and you want the rest of the picture. Reply to it:
scale:bro→ the remaining territory, swept — not another excavation.
Said aloud: “Lingo, scale broad — the whole neighbourhood.”
→ the complete sweep, spoken.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “scale broad”. Dictated directives fire deliberately, never by accident.
What the agent actually does
Lists the territory before answering, gives each part its stop at working size, and holds the breadth discipline: no stop swells into a deep treatment, none thins into a skim. Where the territory is bigger than one reply can honestly sweep, it covers what fits and names what was left outside rather than faking completeness.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-scale-broad ↗.
When the host can't
No host capability required; always executable.
Conformance — “done when”
Nothing in the territory was skipped, and nothing was excavated.
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.