Command Explorer › re: — the reply's form › cite

re:cite

Show this reply's sources, inline with its claims.

Level 2Evidence axisClass: actShortest: ciRequires: nothing beyond conversationPersistence: noneConfirmation in the reply: not required

Directive Shorthand 3.2 · Command explorer · Assembled from the canonical spec, registry, usage guide, and implementation guide — this page adds no meanings.

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

The answer's claims carry their citations inline, so the evidence the answer rests on is visible in the reply itself.

The registry's own words: Show this reply's sources: the claims in the answer carry their citations inline, so the evidence the answer rests on is visible in the reply itself. Cite displays sources; it does not itself perform verification — rigor in the work is the request's business, stated in prose.

Fire it — usage examples

“Is that supplement actually safe with my prescription? re:cite”

→ the answer, with the source behind each load-bearing claim shown in the reply.

An answer lands carrying a claim you want to inspect. Reply to it: re:ci

→ the same answer reissued, sources attached to the claims they support.

Said aloud: “Lingo, reply cite.”

→ the claims, with their evidence visible in the reply.

Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “reply cite”. Dictated directives fire deliberately, never by accident.

What the agent actually does

Display only: the agent attaches to each load-bearing claim the source actually used for it, in the platform's ordinary citation form. cite does not itself commission verification — how rigorously claims were checked is the work's business, chosen by your request in prose.

The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-re-cite ↗.

When the host can't

No host capability required. Where the answer rests on no retrievable source (existing knowledge only), say so in the reply rather than dressing memory as citation; never fabricate a citation.

Conformance — “done when”

Every load-bearing claim in the reply either carries a real citation or is plainly marked as resting on existing knowledge.

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.