Command Explorer › gen: — what the agent makes › graph
gen:graph
A chart or diagram rendered from data — the data is the promise.
What it does
A visual from data as the deliverable: a chart, plot, or diagram rendered from designated data or structure. The artifact stands on its own — its promise is the data, not decoration.
The registry's own words: A visual from data as a deliverable: a chart, plot, or diagram rendered from designated data or structure — an artifact whose promise is the data, not decoration.
Fire it — usage examples
“Chart the year’s revenue by month from this sheet.
gen:graph”→ the chart is rendered from the data and delivered as an artifact.
“Which month was best?
re:show” answers in the reply, with a chart. “Make me the chart for the report.gen:gr”→ the chart itself is the deliverable — made to be kept and sent, not to carry this reply’s answer.
Said aloud: “Lingo, generate graph — revenue by month.”
→ the rendered chart is delivered.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “generate graph”. Dictated directives fire deliberately, never by accident.
What the agent actually does
The agent takes the designated data or structure, chooses the honest rendering for it (chart, plot, diagram), renders it, and delivers the visual as an artifact. The numbers in it are the designated numbers, exactly — a graph that decorates rather than renders is a failed gen:graph. Where the host cannot render, it delivers the data table plus the chart specification, disclosed as unrendered.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-gen-graph ↗.
When the host can't
No rendering capability for graph on this host: disclose it plainly and never fake a chart. A natural partial: deliver the data table plus the chart specification, disclosed as unrendered — a description of the chart alone is not the graph.
Conformance — “done when”
The rendered visual is delivered with the designated data intact, or the disclosed partial (table + specification) is delivered instead.
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.