# Presentation Pack — one-prompt cinematic decks, brand-locked, editable by talking

> **PORTABILITY NOTE (added 2026-07-27).** This process doc is published from Imperium's
> internal operating system. The METHOD is fully portable: prompts, model choices and
> parameters, CSS/SVG recipes, QA gates, and cost discipline all work anywhere. Paths that
> start with `~/.claude/`, `<repo-root>/`, `presentations/`, `scripts/`, or `memory/` are
> internal conveniences on the author's machine; substitute your own equivalents (any
> headless-browser screenshot loop, any image toolchain). Same for internal distribution
> steps (Google Drive folder IDs, Telegram bots) and `<your-vercel-team>` deploy scopes:
> use your own storage, messaging, and hosting. Working style anchors ship WITH this kit
> in `../cards/`, `../console/`, and `../folder/` — start from those, not from zero.

> Assembled 2026-07-07. The productized layer on top of `presentations/continuous-world-kit/` (the engine + mission that built https://aios-v2.imperiumos.ai overnight in one prompt). Purpose: a non-expert speaks plainly ("this is what I want"), and the system produces a premium web presentation on a public link, adhering to their company's brand guidelines, and lets them change it by prompting.

## The promise, honestly stated

- One conversational brief → one self-contained mission → generated world + film transitions + HTML type → public Vercel link → Telegram'd back.
- The user never writes a "prompt". The intake SOP converts speech into the mission's parameter block; the SOPs carry "what good looks like" so taste is baked in, not required.
- The ONE mandatory human moment: approving the pilot still + one styled slide screenshot before the batch (5 minutes). Skipping it is how brands drift and credits burn. Everything else can run unattended.
- Cost reality: a full 10-slide continuous-world deck runs 600-1,000 Higgsfield credits and 4-8 hours of agent runtime. Static-background decks (no films) run under 150 credits and ~1 hour. The intake asks which tier the moment deserves.

## The stack (what does what)

| Layer | Tool | Job |
|---|---|---|
| Orchestration + code + QA | Claude Code (Fable 5) | reads the pack, generates, builds the app, screenshots, iterates, deploys |
| World stills | Higgsfield MCP → GPT Image 2, 4k/high | slide backgrounds, chained refs for one-world consistency |
| Transition films | Higgsfield MCP → Seedance 2.0, 1080p std | start/end-frame camera moves between slides |
| Type, cards, diagrams, charts | HTML/CSS/React (never diffusion) | everything containing words or data |
| Live product | iframe | real UI is never faked |
| Delivery | Vercel (public team) + Telegram | shareable link in the room |

## Files (read order for an agent running a deck)

1. `01-intake-sop.md` — plain-speech brief → parameter block (the question battery + tier router)
2. `02-brand-styling-sop.md` — brand kit in → `stylings/<brand>.md` skill out. THE load-bearing SOP: brand adherence is the product.
3. `03-design-quality-sop.md` — the anti-AI-look laws: type, backgrounds, motion, composition, copy
4. `04-model-routing-sop.md` — locked model choices (verified 2026-07-07) + verification discipline + new-parameter gotchas
5. `05-edit-by-prompt-sop.md` — change requests routed to the cheapest layer that satisfies them
6. `styling-template.md` — the fill-in per-brand styling file (instantiate once per brand: ELLE, Wilder, GeoNet, …)
7. `../continuous-world-kit/MISSION-TEMPLATE.md` + `TECHNIQUE.md` — the engine: mission anatomy, transition machine, encode, deploy, QA, cost model, pitfalls

## Quickstart (agent)

1. Run the intake battery (01) → fill `MISSION-TEMPLATE.md` slots + pick/build the brand styling (02).
2. Pilot: still 01 (2-3 candidates) + one fully styled slide screenshot → **human approves**.
3. Batch generation → build app (copy `aios-walkthrough-v2/web/`) → QA loop (03 scores + TECHNIQUE §8) → deploy → notify.
4. Changes arrive as plain speech → route via 05.

## Per-client packaging note

Brand stylings are per-client skill files instantiated from `styling-template.md`; the pack itself stays client-agnostic. A client install ships the pack + their stylings + the kit.
