# Novel Storyboard - Agent Guide

Execution-packet remap of a Toonflow-inspired creative pipeline into a desirable novel-to-storyboard product: cinematic shot frames, episode planning, script/assets, storyboard flow, media tasks, preview export, and safety gates.

## Agent instruction

Do not scrape the human UI. Use this agent guide, the package manifest, and raw Buildprint files.

1. Fetch package manifest: `/buildprints/novel-storyboard/package.json`
2. Read order: `BUILDPRINT.md` -> `01-questions.md` -> `02-project-setup.md` -> `blueprint.yaml` -> `03-phases/phase-index.yaml` -> `03-phases/01-canvas-workbench.md` -> `04-evaluation.md` -> `05-evidence/evidence-ledger.jsonl`.
3. Do not scrape human cards. Use this manifest, agent.md, and raw files. BUILDPRINT.md is the canonical execution authority. Complete 01-questions.md and 02-project-setup.md before phase work; blueprint.yaml and other structured files are machine-readable mirrors/routers, not competing instructions.
4. Follow the Buildprint's alignment/question rules before implementation.
5. Run required validation and write requested validation evidence plus the final chat handover.

## Metadata

- slug: `novel-storyboard`
- category: `Mapped Project`
- tier: `agent-grade`
- status: `validated`
- runtime: Executable packet, Mock-first AI providers, Browser QA
- stack: BUILDPRINT start, Product vision, Phase packets, Evidence ledger, Preview manifest export

## Entrypoints

- Human page: /buildprints/novel-storyboard/
- Manifest JSON: /buildprints/novel-storyboard/package.json
- Prompt: /buildprints/novel-storyboard/prompt.txt
- GitHub: https://github.com/DomEscobar/agent-buildprint/tree/main/buildprints/novel-storyboard
- Raw base: https://agent-buildprint.com/buildprints/novel-storyboard/files

## Files

- `01-questions.md` - Buildprint package file (required)
- `02-project-setup.md` - Buildprint package file (required)
- `03-phases/01-canvas-workbench.md` - Buildprint package file (required)
- `03-phases/02-flow-persistence.md` - Buildprint package file (required)
- `03-phases/03-production-agent-loop.md` - Buildprint package file (required)
- `03-phases/04-media-generation.md` - Buildprint package file (required)
- `03-phases/05-webapp-runtime.md` - Buildprint package file (required)
- `03-phases/phase-flow.md` - Buildprint package file (required)
- `03-phases/phase-index.yaml` - machine-readable mirror (required)
- `04-evaluation.md` - Buildprint package file (required)
- `05-evidence/evidence-ledger.jsonl` - Buildprint package file (required)
- `05-evidence/evidence-ledger.schema.json` - machine-readable mirror (required)
- `blueprint.yaml` - machine-readable executable packet router (required)
- `BUILDPRINT.md` - compatibility bootstrap or package contract (required)
- `checks/acceptance.md` - acceptance checklist (required)
- `CONTRACTS.md` - legacy interface/data contracts, when present (required)
- `generated/agent-prompt.md` - Buildprint package file (required)
- `PLAN.md` - legacy execution index, when present (required)
- `publication.json` - machine-readable mirror (required)
- `README.md` - human overview, non-authoritative (required)
- `SPEC.md` - legacy behavior requirements, when present (required)
- `TEST_MATRIX.md` - legacy risk-to-test alignment, when present (required)
- `VALIDATION_TEMPLATE.md` - legacy completion report template, when present (required)

## Copyable implementation prompt

```txt
Use the Novel Storyboard Buildprint. First bootstrap exact snapshots: agb start https://agent-buildprint.com/buildprints/novel-storyboard/package.json . If agb is not installed, clone https://github.com/DomEscobar/agent-buildprint and run node agent-buildprint/bin/agb.js start https://agent-buildprint.com/buildprints/novel-storyboard/package.json . Then read .buildprint/next-agent.md and continue. Do not write Buildprint snapshots manually. The bootstrapped packet is the source of truth — follow its read order (BUILDPRINT.md, 01-questions.md, 02-project-setup.md, blueprint.yaml, 03-phases/phase-index.yaml, 04-evaluation.md, and the active phase files) instead of restating its rules here.
```