The frame nobody shot
Mira finds a frame in Reel 3 that was never on the camera report.
The design system behind Kwark, the story workspace for filmmakers. Every rule, token and component is written once and published twice: as pages for the people who design and build, and as context for the agents that build with them.
Every value Kwark uses is a named token. Pick a basic to see the values, the rules for using them, and the mistakes they prevent.
Principles, foundations and patterns, each with the reason behind it and the decision record that settled it.
One CSS file, the shared React components, a theme token manifest, and tests that fail when a file drifts.
AGENTS.md, an MCP server, prompts, a design-to-code handoff and readiness tests that show whether your agent follows the system.
Kwark never scores, judges or rewrites a writer's work (Decision 0002). When it proposes something, like a scene heading taken from your own outline beat, it marks it the way film marks a revised line: a star in the margin and a dotted rule, until you accept it or make it yours. Edit the heading and watch the mark give way.
Read AI and authorshipYour outline beat: Mira finds the splice in the edit suite, night.
Most systems describe how an interface looks. This one also says who may change a writer's words, which decision a rule comes from, and what an agent must prove before its code ships.
A machine may find, move or carry the writer's words. It never writes, scores or judges them (Decision 0002), and the tests say so.
Rules trace to numbered decision records with the problem, the options, the choice and the date.
Every page has a markdown twin and a readiness test, plus AGENTS.md, W3C tokens, an MCP server and skills.
Screenplay pages that print, stripboards, call sheets with numbered revisions, and kits for editing, grading and sound.
Devanagari, Tamil and Latin on one page, and five writing rooms with the contrast worked out.
No scores or leaderboards, sharing by film role, one header line and one button on a phone.
Loading…