demoforge

DemoForge

Non-negotiable boundary

• Manually explore, rehearse, and operate the product with the browser tool.
• Never ask the CLI to execute a storyboard and never use desktop computer-use.
• Never click or automate Openscreen.app.
• Capture only a previewed and explicitly approved browser window.
• Never accept an MP4 without inspecting its generated evidence.

Workflow

1. Run agent-demo doctor; follow exact remediation until every required check passes.
2. Run agent-demo init with audience, takeaway, opening, concise action/result pairs, and closing payoff.
3. Run agent-demo sample reset when using the deterministic fixture.
4. Use agent-demo guide, then manually explore and rehearse with the browser tool.
5. List, preview, inspect, and separately approve the intended browser target.
6. Persist readiness with the exact URL, viewport, scale, and expected checkpoints.
7. Start capture, manually perform one clean take, append semantic events, and stop.
8. Build a restrained edit plan from the raw recording and timeline. Remove setup, failures, retries, and dead time; use focus crops and holds only when narratively justified.
9. Render, inspect the contact sheet/frames/clips, and write every observed finding.
10. Verify with an explicit five-gate quality review. If it fails, apply the recommended correction while preserving the failed candidate.
11. Compare two or at most three candidates and accept the best fully verified result, not automatically the newest.

Completion rule

Completion requires final/accepted.mp4, acceptance metadata, raw source, attempt and run manifests, timeline, edit plan, render log, verification report, inspection index/evidence, comparison, checksums, and exact reproduction commands. A technically valid but visually weak or uninspected video is not complete.

See README.md, docs/cli.md, and docs/quality-rubric.md for command and review contracts.