CROSSFRAME

Twitch already merged the chat. We merged the space.

Comment

Two streams. One physical space.

CROSSFRAME explores a new collaboration primitive for Twitch: separate broadcast overlays become adjacent viewports into one server-authoritative world. A luminous Signal carries the same identity, visual seed, position history and velocity as it crosses the seam. In the full collaboration design, Shared Chat source provenance determines which community can control the Signal in its region.

What the demonstration shows

The demonstrated mode is SOLO PREVIEW: one authenticated broadcaster supplies real Twitch chat input, while an explicitly labeled SIMULATED PARTNER operates the second region. Real !launch, !up and !reverse commands reached the authoritative server through Twitch EventSub. The same Signal crossed A → B, returned after a simulated partner command, then crossed again and triggered the server's finale state. The two-broadcaster Shared Chat mode is implemented and fixture-tested but has not been live-verified with two broadcasters. Independent Twitch video delivery can introduce different player delays, so synchronized world state is not a promise of frame-perfect video playback.

The Node.js server owns the fixed-step simulation, boundary transitions, command provenance and deduplication. Transparent browser-source viewports render its snapshots. A PostgreSQL checkpoint encrypts the world, overlay capabilities and dashboard sessions; a hosted redeploy recovered the same world, Signal and transfer history, and real Twitch commands continued to affect it afterward. The broadcaster reported that both overlay windows and embedded Twitch chat loaded after the restart; continuity of the original overlay URLs and the visible finale still need verification.

How we used Codex

Codex contributed the TypeScript implementation, Twitch OAuth and EventSub integration, procedural canvas visuals, PostgreSQL persistence, tests, debugging and delivery documentation. Automated coverage includes 100 identity-preserving transfers, provenance and retry handling, real local PostgreSQL recovery, and two-renderer browser tests. Fixture and synthetic-event results are identified separately from real Twitch evidence. The project does not use a runtime language model.

Built With

Share this project:

Updates