Command Explorer › gen: — what the agent makes › site
gen:site
A website — pages built, and published where the host can.
What it does
A website as the deliverable: pages built and, where the host can, published — a place to be visited, not a description of one.
The registry's own words: A website as a deliverable: pages built and, where the host can, published — a place to be visited, not a description of one.
Fire it — usage examples
“A one-page site for the piano-moving service, with the quote form.
gen:site”→ the site is built and, where the host can publish, published — the reply carries the address.
“Build the FAQ page we drafted, as its own site.
gen:si”→ the pages are built and delivered; where the host can build but not publish, the files are delivered, disclosed as unpublished.
Said aloud: “Lingo, generate site — the piano-moving page.”
→ the site is built, and its address (or its files) delivered.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “generate site”. Dictated directives fire deliberately, never by accident.
What the agent actually does
The agent builds the designated pages — content, structure, the designated features — and publishes them where the host has a publish path, delivering the address. No publish path → the built files are the deliverable, disclosed as unpublished; a mock-up or a description is not a site.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-gen-site ↗.
When the host can't
No generation capability for site on this host: disclose it plainly, never fake a published page or a link, and never silently substitute a description of a site for one. A natural partial: where the host can build but not publish, build the site and deliver its files, disclosed as unpublished.
Conformance — “done when”
The site is built and published (address delivered) or built and delivered as files, disclosed as unpublished.
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.