LocationInstallation boundary
Top-level container for venues, operators, and the installation’s shared context.
Technical brief / build 0.1
Victory is a browser-based virtual tabletop with a persistent content model, a live-session runtime, and authoring surfaces for building game-specific rules and material into the application.
The current system boundary is a static public website plus a separately deployed live application. The website is a Cloudflare Pages deployment. The live Victory application is a runtime composed of browser clients, Go services, PostgreSQL persistence, WebSocket session state, and a stage renderer.
The system separates durable production data from a live Showing. A Show is the persistent production; a Showing is an instance of that production; Showtime is the active live state.
| Client UI | HTML/CSS/JavaScript with Vue for interaction-heavy surfaces |
|---|---|
| Renderer | PixiJS stage composition |
| Services | Go application and domain packages |
| Persistence | PostgreSQL |
| Realtime | WebSocket session synchronization |
| Public site | Static HTML on Cloudflare Pages |
| Component | Implementation | Responsibility | Status |
|---|---|---|---|
| Shared frontend shell | Browser client | Navigation, identity, access boundaries, and shared application surfaces. | Active |
| Stage runtime | PixiJS and client state | Maps, tokens, drawings, cues, and other stage objects during live use. | Active alpha |
| Domain services | Go | Show, Showing, roster, participation, content, and permission operations. | Active alpha |
| Live synchronization | WebSockets | Propagation of session state between connected clients. | Active alpha |
| Discord surfaces | Discord bridge and mapped voice state | Presence, chat, and audio-adjacent integrations where configured. | Partial / environment-dependent |
A live session moves from persistent Show content to a scheduled Showing and then to active Showtime state. The browser renders the state appropriate to the participant’s role while the application services remain responsible for persistence and authorization.
LocationTop-level container for venues, operators, and the installation’s shared context.
ShowCampaign or game instance containing title, roster, scenes, rules, and authored material.
ShowingA scheduled or audience-facing performance of a Show.
ShowtimeThe active state of a Showing while clients are connected and the stage is running.
Content is authored in eWrite, organized through Storyboards and production surfaces, and reused through the Library and Workshop rather than being reconstructed inside each live session.
eWriteMarkdown-based manuscripts, Rulesets, and Skill Directories.
StoryboardsCards, columns, rows, bands, and production structure before live staging.
Library / WorkshopScenes, assets, metadata, composition, storage, and permissions.
Greenroom / TrailersCharacter, player, profile, and participation surfaces associated with a Show.
The intended product direction is system-agnostic at the platform level and game-specific at the content level: a game’s rules and authored material should be usable inside the VTT instead of being reconstructed from generic components for every session.
The public explainer and the live application are deployed separately. This keeps public documentation and release links available even while the live runtime changes during alpha development.
Static product information, comparisons, licensing references, and release links.
Go services, PostgreSQL, WebSockets, Caddy, and browser clients.
Installer with automatic update support through the public release repository.
Podman deployment materials are available; no packaged Debian installer is currently published.
browser client
├── HTTP / application requests ──> Go services ──> PostgreSQL
├── WebSocket session state ──────> live Showing state
└── local renderer ───────────────> PixiJS stage composition
authoring surfaces ──> persistent Show content ──> Showing ──> Showtime
Discord integration ─> optional presence / chat / voice-adjacent state
Engineering history and milestone records are maintained in the Victory repository’s Construction/History directory ↗.
Persistent state belongs to a Location or Show: authored manuscripts, rulesets, scenes, rosters, assets, and production structure. A Showing references that material for a particular session. Showtime is the transient live state produced while participants are connected.
Clients do not need the same interface surface. Audience, Cast, Director, Producer, Crew, and Author roles are different access and presentation contexts over the same running production. The current alpha is still refining the boundaries between role permissions, content visibility, and live controls.
That distinction is also why the product is not described as a collection of unrelated panels. Authoring and preparation are intended to produce durable material that the live runtime can consume, while live interaction should not silently replace the canonical authored source.
Assume a public alpha, changing interfaces, and incomplete operational documentation. The current site describes the implementation that exists or is actively represented in the repository; it does not promise feature parity with established VTTs, production uptime, or a finished content ecosystem.
For a meaningful evaluation, build a small scenario, author the rules and reference material, run one Showing, and record where the workflow requires manual reconstruction. Those observations are more useful than comparing isolated features such as maps, lighting, chat, or player views, which are common across virtual tabletops.
Engineering history, release artifacts, and licensing documents remain the authoritative references for their respective subjects. This brief is a current implementation summary and should be updated when those sources change.