StoryFlow Overview

🦞🎬 StoryFlow — Studio Shell on omp

Thesis: omp is the body; StoryFlow is the always-on shell that probes, casts, produces, molts — and its face is one daemon, one port, three surfaces.

flowchart LR
  subgraph FACE["Face — three surfaces, one bundle"]
    W["Web app<br/>SvelteKit SPA"]
    P["Side panel<br/>WXT · Chrome"]
    M["Phone PWA<br/>monitor + approve"]
  end
  G["Gateway · Bun<br/>WS · REST · SQLite · queue · registry"]
  W --> G
  P --> G
  M --> G
  subgraph HOOD["Under the hood — the molty loop"]
    SH["Shell<br/>profile · channels · heartbeat"] --> RG["Registry<br/>capabilities.yml"]
    RG --> CA["Cast<br/>director · writers · refuters · crew · media"]
    CA --> GR["Grammar<br/>brief to bible to shots to assets to QA to ship"]
    GR --> MO["Molt<br/>learn · skills · extensions"]
    MO -.-> RG
  end
  G -- "JSONL stdio · rpc v2" --> O["omp --mode rpc<br/>--profile storyflow"]
  O --> SH
  G --> PR["Providers<br/>veo · grok-imagine · codex-images · xai-tts · ffmpeg · flow-relay"]

Section 0: One Breath

StoryFlow is an always-on studio agent running on omp 18.2.6:

1. Probes what it can do right now through live host probes.
2. Casts models like a film crew across different provider families.
3. Produces from a one-line logline to a shipped deliverable through one unified grammar.
4. Molts (grows its own shell) after every run by harvesting lessons and skills.

The system face consists of one local daemon on one port (7540) serving three surfaces:

• 🖥 Web app: SvelteKit 2.x SPA (adapter-static with fallback) using Svelte 5 runes and Tailwind 4 + daisyUI 5.
• 🧩 Chrome side panel: WXT extension shell sharing packages/ui with WebSocket in the service worker.
• 📱 Phone PWA: Mobile web view for monitoring and human approvals on the go.

FlowTurbine, the batch generator from the archive, survives inside StoryFlow as the Queue tab, done properly with per-item retry backoff, pre-flight cost calculation, seed lock, and asset provenance.

The Two Human Gates

StoryFlow enforces an automated swarm pipeline with exactly two human gates:

1. Bible Veto Gate (Pre-Production): The Director model compiles the project bible, character sheets, and scene specs. Production halts until human sign-off via extension_ui_request / Approvals tab.
2. Ship Gate (Post-Production): Independent QA agents grade the rendered artifacts against blockbuster metrics. The final release and market dispatch require explicit human authorization.

Core Wiki Navigation

• StoryFlow Bible: Full import of Sections 1–4 of the cheatsheet SSOT.
• Implementation Plan: TaskList and ten-moves execution ledger.
• Architecture & Protocol: Daemon architecture, Gateway-omp RPC v2 bridge, and protocol envelopes.
• Decisions & Refuter Rulings: The 12 refuter rulings and D-134 operating parameters.
• Progress Log: Step-by-step milestone log.
• Verification Receipts: Executable proof commands and test outputs.