Build in public
What is real, what is wiring, what is next.
This board is generated from the same status file the product ships with. A phase reads live only after its test gate, verification gate, and ship gate pass. The site cannot claim a feature before the repository proves it.
12 of 12 phases live · updated 2026-07-02
- Live
Phase 0: Model landscape
Video and image model registry with intent-aware routing policy.
- Live
Phase 1: Vertical slice
Idea to directed shot to guarded render path with provenance.
- Live
Phase 2: Multi-model router
Per-shot routing across Kling, Veo, Seedance, Runway, and Luma paths.
- Live
Phase 3: No-drift continuity
Locked character, style, and lighting references across every shot.
- Live
Phase 4: Story Intelligence
Hook, arc, shot purpose, mute test, and attention-cut checks before render.
- Live
Phase 4.5: Trust and safety
Policy checks, consent gating, provenance, watermarking, and audit logs.
- Live
Phase 5: Brand Memory
Locked brand facts, URL ingest, and continuity-ready product references.
- Live
Phase 5.5: Director Modes
Fourteen camera grammars with auto selection from the creative brief.
- Live
Phase 6: Agent surface
REST, MCP, plugin, skills CLI, guided prompts, and server-issued scoped tokens.
- Live
Phase 6.2: Profiles and auth
Supabase Google, GitHub, magic link auth, and editable creator profiles.
- Live
Phase 7: One-tap publish
Platform previews for TikTok, YouTube, Instagram, and Facebook with explicit confirmation.
- Live
Phase 8: Share and remix
Public direction pages, brand scrubbing, remix handoff, pricing, quality feedback, and failover.
The three open seams
We would rather state these plainly than let the site oversell. Each is a designed boundary in the code, ready for credentials, not a rewrite.
Live provider renders
The full planning, safety, continuity, routing, and provenance path runs today. The final call to each video model provider is an injectable seam awaiting provider billing approval. Until it is wired, generation is a beta preview and the interface says so.
Live payment checkout
Billing tiers are published configuration and the checkout boundary exists. The live payment call is not wired, so paid checkout honestly returns a not-configured response instead of pretending to charge.
Live platform posting
Publish previews, per-platform export derivation, the safety gate, and the confirmation gate are complete and tested. The final HTTP post to each platform is an injectable seam awaiting per-platform OAuth app credentials.