Command Explorer › gen: — what the agent makes › essay
gen:essay
An essay — an argued piece on a designated subject.
What it does
An essay as the deliverable: a piece that argues one thesis on a designated subject, in the voice the active style: carries — produced and delivered as a durable artifact.
The registry's own words: An essay as a deliverable: license prose that answers to its thesis — an argued piece in a voice, the register carried by style: — produced as a written artifact in its own form, not as prose in the reply. Minted in 3.9 under the deliverable test: an essay is judged by whether it argues its thesis, a discipline no sibling kind carries.
Fire it — usage examples
“Why every agent should ship with its tools — make the case.
gen:essay”→ an essay is drafted to its thesis and delivered as an artifact; the reply confirms it.
“The case against meetings, as an essay.
gen:ess”→ one thesis, argued — not a neutral explainer; that would be gen:doc.
Said aloud: “Lingo, generate essay — the case for the four-day week.”
→ the essay is produced and delivered as an artifact.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “generate essay”. Dictated directives fire deliberately, never by accident.
What the agent actually does
The agent fixes the thesis in one sentence before drafting, then drafts to it — the argument’s line, its evidence in service of the thesis, its register from the active style: state — and delivers the piece as a durable artifact.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-gen-essay ↗.
When the host can't
No generation capability for essay on this host: disclose it plainly and never silently substitute a report, a document shell, or reply prose for the essay. A summary of an argument is not the essay.
Conformance — “done when”
An essay is delivered as an artifact, its thesis visibly argued — or the missing capability is disclosed.
Persistence class: content-write. Execution report in the reply: 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.