01
Live theaters
Catharsis, First Theater, and Victory Theater are live-performance venues built on the same stage runtime. They hold maps, tokens, cues, drawings, and other stage objects.
Product explainer / public draft
Victory is a virtual tabletop theater.
Victory combines live, role-aware stage venues with the tools needed to write, plan, store, and revisit a production.
Working definition
Victory is built for stories that have a world behind them and a performance in front of them. The live theaters power the VTT, while Storyboards, writing tools, the Library, and production spaces support everything that happens before and after a Showing.
01
What Victory contains
02
Storyboards
A spatial planning surface for arranging cards, columns, rows, and bands before material is placed on the live stage.
03
Writing tools
eWrite is Victory’s Markdown-based authoring system for manuscripts, Rulesets, and Skill Directories. Writer’s Room is where this work is written and revised.
04
Library and assets
Library holds reusable Scenes and reference material. Workshop and Warehouse support asset composition, storage, metadata, and permissions.
02
How the product is organized
These terms describe different levels of the system. A Show persists over time; a Showing is one performance; Showtime is the live state of that performance.
Location
The lotOne installation’s top-level container: venues, people, and its Operator.
Venues
Live theaters · Storyboards · Library · Writer’s Room · Greenroom · Producer’s OfficeShow
The productionTitle, roster, Scenes, Storyboards, and rules-native content.
Showing
The performanceOne scheduled or audience-facing performance of a Show.
Showtime
The live stateThe stage is running and each participant receives the appropriate projection.
03
From authored material to live play
1
Write and define
Use eWrite for manuscripts, Rulesets, and Skill Directories. This is the rules and reference layer.
2
Plan the production
Use Storyboards to structure cards and events, and the Library to keep reusable Scenes and reference content available.
3
Prepare the Showing
Producers and Directors handle roster, scheduling, Scenes, cues, and other production work in the backstage venues.
4
Run the Showtime
The live venue composes the stage and synchronizes the session. Cast, Crew, Directors, and Audience see the parts intended for them.
04
Who uses which layer?
Role or groupPrimary concernRelevant surfaces
AudienceWatch a specific ShowingLive theater, audience projection, Guide / chat pod
CastPlay a Character in a ShowLive theater, Greenroom, Storyboards when opened to the production
Director / ProducerRun and manage the productionDirector’s Chair, Producer’s Office, Stage Management, live theater
CrewPerform bounded backstage tasksStoryboards, Workshop, cue and content tools
Authors / designersWrite and structure the worldWriter’s Room, eWrite, Storyboards, Library
05
Technical outline
Frontend
Static HTML/CSS/JavaScript surfaces, Vue for newer interaction-heavy venues, and PixiJS as the renderer for stage composition.
Backend
Go services with domain packages for access, participation, Show Runs, Scenes, Storyboards, eWrite, and related concerns.
State
Postgres persistence for accounts, productions, rosters, Scenes, permissions, and authored content; WebSockets for live session synchronization.
Integrations and serving
Discord identity, chat, and audio surfaces; Caddy serves the frontend and routes application traffic. See the full technical brief for the current system shape.
Public draft
Open the feedback form
Something unclear or missing?
This explainer is meant to be useful to people who did not build Victory. Use the feedback form to point out confusing language, missing context, or technical details that should be documented here.