Files
storyforge/concepts/studio-workbench
kris 65db3cd336
Some checks failed
StoryForge CI / Baseline checks (push) Has been cancelled
StoryForge CI / Backend tests (push) Has been cancelled
StoryForge CI / Web tests (push) Has been cancelled
chore: sync storyforge handoff state
2026-05-02 17:50:21 +08:00
..
2026-03-14 21:35:30 +08:00
2026-05-02 17:50:21 +08:00

Version B: Studio Workbench

Direction: Castmagic x content ops studio

Preview prototype: index.html

This version optimizes for teams that want to turn one material source into many structured outputs.

Product thesis

  • Users should feel they are operating a content studio, not just a summarizer.
  • Material ingestion is one panel inside a broader production system.
  • Knowledge bases, assistants, and output assets should be visible at once.
  • This is stronger for repeatable workflows and team collaboration.

Key decisions

  • Production becomes the emotional center of the app.
  • The screen is split into material, assistant, and output zones.
  • The user can see which knowledge bases feed which assistant.
  • One source material can drive multiple output formats immediately.
  • This layout is heavier, but it better communicates long-term business value.

When this version is best

  • Small content teams
  • Agencies managing multiple client voices
  • Users who need assistant governance and model routing
  • Teams that value throughput over the fastest first-use experience