Command Explorer › gen: — what the agent makes › video

gen:video

A video — moving images, delivered as an artifact.

Level 2Kind axisClass: actShortest: viRequires: generationPersistence: content-writeConfirmation in the reply: required

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

What it does

A video as the deliverable: moving images, with sound as the message designates — a clip, an animation, an explainer — produced as an artifact.

The registry's own words: A video as a deliverable: moving images, with sound as the message designates — a clip, an animation, an explainer — produced as an artifact.

Fire it — usage examples

“A thirty-second explainer of how the deposit works. gen:video”

→ the video is produced and delivered as a playable artifact.

“Animate the route map for the crew briefing. gen:vi”

→ an animated clip is delivered — a still of the map would be a different kind.

Said aloud: “Lingo, generate video — the deposit explainer.”

→ the video is produced and delivered.

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

What the agent actually does

The agent produces the designated video — subject, length, sound as designated — and delivers it as a playable artifact. A storyboard, a still, or a description may be offered as a disclosed partial where production is impossible, but none is presented as the video.

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

When the host can't

No generation capability for video on this host: disclose it plainly, never fake a video, and never silently substitute a still image, a storyboard, or another kind for it. A description of the video is not the video.

Conformance — “done when”

The video is delivered as a playable artifact, 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.