Command Explorer › re: — the reply's form › list
re:list
Present the material as an enumerated set — items on their own lines, each one complete; the form for a set, where steps is the form for a sequence.
In the re: domain
re:voice — Reply with a voice note (spoken audio).re:show — Answer visually instead of in prose.re:recap — Catch me up: state, decisions, what's open.re:steps — A numbered procedure, one action per step.re:list — Present the material as an enumerated set — items on their own lines, each one complete; the form for a set, where steps is the form for a sequence.re:cite — Show this reply's sources, inline with its claims.What it does
Presents the material as an enumerated set — items on their own lines, each complete in itself. Membership is the meaning; where order is the meaning, that's steps.
The registry's own words: Present the material as an enumerated set — items on their own lines, each one complete; the form for a set, where steps is the form for a sequence.
Fire it — usage examples
What do we still need for the move?
→ re:list
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is reply list. Dictated directives fire deliberately, never by accident.
What the agent actually does
Itemizes instead of narrating: one framing line at most, then the set. Material that needs a paragraph is pulled out and treated in prose after the list — never padded into an item. If there's no set to enumerate (one item, or material that's really a sequence), says so and answers in the fitting form.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-re-list ↗.
When the host can't
None specific. If there is no set to enumerate — a single item, or material that is really a sequence — say so and answer in the fitting form rather than padding a one-item list.
Conformance — “done when”
The reply is the set, itemized — each item complete on its own line.
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.