← Back to registry
Product OS Advanced by Agent Buildprint

Portable Novel-to-Storyboard Pipeline

Build a deterministic novel-to-storyboard pipeline that agents can implement end-to-end before expanding into live providers.

Open manifest GitHub folder

methodology

agent-ready
01 Contract spine
02 Implementation phases
03 Validation gates
04 Prompt handoff

Executable packet spine

The files or runtime artifacts a fresh agent must read or produce before claiming progress.

  • AGENT_HANDOFF.md
  • AGENT_PROMPT_PACK.md
  • ASYNC_JOB_MODEL.md
  • BROWSER_QA_SCENARIOS.md
  • BUILDPRINT.md
  • CONTRACTS.md
  • HEAD_TO_FOOT_QA.md
  • README.md
  • SPEC.md
  • PLAN.md
  • TEST_MATRIX.md
  • VALIDATION_TEMPLATE.md
  • checks/acceptance.md

Proof gates

Checks that prevent a vague implementation from being reported as complete.

  • ✓Default CI uses mock/no-network providers
  • ✓3 fixture chapters complete successfully
  • ✓Malformed outputs are rejected safely
  • ✓Unimplemented capabilities are excluded

Risks covered

Failure modes the Buildprint makes visible before an agent can hide them in “done”.

  • ⚠Malformed XML corrupting state
  • ⚠Placeholder controls
  • ⚠Live-provider claims without gates

What this ships

01

Chapter import

02

Event extraction

03

ScriptAgent stages

04

Asset extraction

05

Storyboard validation

Validation evidence

For newer phase-flow Buildprints, this names replay or outcome evidence. For older registry entries, it lists the included validation checks.

  • Default CI uses mock/no-network providers
  • 3 fixture chapters complete successfully
  • Malformed outputs are rejected safely
  • Unimplemented capabilities are excluded

Copyable agent prompt

Manifest 
Use the Agent Buildprint: Portable Novel-to-Storyboard Pipeline.

Bootstrap it with `agb start https://agent-buildprint.com/buildprints/portable-novel-storyboard-pipeline/package.json ./my-build` or inspect the GitHub folder. Follow BUILDPRINT.md as the authority spine, read the supporting contracts/checks before implementation, preserve the stated non-goals and safety gates, and do not claim completion until the included validation checks pass.