Creative variety
One archetype per item, never a batch-wide template. Every piece of content gets its own composition, chosen from the registered set for its platform.
USE CASE · AI DESIGN DEPARTMENT
Visual production
on the live loop.
Design is a production department on the SpielOS loop. It takes one shared campaign Artifact, picks a registered creative archetype per item and platform, renders previews first, and ships verified flat-motion videos and Threads graphics with evidence.
THE DEPARTMENT
How the Design department works.
Six steps from campaign Artifact to registered creative, enforced by the same runtime that runs this website.
- 1
Goal intake - Design accepts only the shared campaign Artifact and the One Idea inside it
- 2
Archetype gate - every item picks a registered archetype of the platform's kind: shorts for YouTube, social for Threads
- 3
Rotation - no batch repeats a template, and both experiment cells stay balanced
- 4
Preview-first - renders land in the review gallery before anything is approved or registered
- 5
Vision QA - every composition is checked against the design system and semantic tokens
- 6
Registration - a new archetype enters the registry only with a parseable template and documented research
The workflows that run it.
The department declares four workflows. These three give the output its shape.
Rotation gate
A mechanical gate rejects any order that repeats a template inside a batch or starves an experiment cell. There is no silent fallback.
Narration pipeline
One persona voice, measured scene timing from the spoken clips, a provider chain, and a 14.9-second budget. No music, no mixed voices.
Video orders end-to-end
Intake, idea lock, one-persona narration, render, QA: a video order runs start to finish as one tracked workflow.
The agents.
Two bounded roles execute the department's work orders. They claim steps, activate skills, and record evidence.
Designer
Composes social visuals and rendition packs for every platform size in a campaign.
Video producer
Renders and verifies flat-motion videos and runs video orders end-to-end.
The skills.
Reusable methods the agents activate for each step.
spielos-ui
Semantic tokens, shared components, and the visual contract every render must follow.
video-creation
HTML-to-video production with measured scene timing and silent previews before narration.
Connections.
Design holds no external credentials.
The department deliberately owns no external connections. Its only input is the shared campaign Artifact, and renders stay local until a handoff records a verified asset URL. Tool access lives where it is needed most: at the campaign and publishing layer, not inside design.
Artifacts.
Every run writes evidence, not just output.
Render report
One report per campaign covering every item and platform pair, with templates, themes, and platform presets verified.
Approved design
The completed social visual, counted only after it passes the QA gates.
Video render
Base render plus audio mix, poster, and CTA frame, delivered as one verified set.
CHANGES LIVE The gallery is rebuilt
The gallery is rebuilt
from the registry at every deploy.
This case and the template gallery read the live archetype registry at build time. Register a template inside the Design department and the public asset updates on the next deploy - no page edit needed.
- The archetype list comes from the registry, never from the page
- A new registered archetype appears on the next build
- Legacy entries are never removed or renamed
- Renders under public/design-gallery/ are the committed assets
Want this discipline in your company?
The Agent Brief maps one of your workflows to the same loop, approvals, and evidence.
Apply — Free Review