torikata. TDD pairing studio
Join with a code Admin Open a room →
TDD · pair programming · katas

Red.
Green.
Refactor.
Together.

Torikata is a real-time studio for engineers who train with intent. — Open a room, pick a stack, share the terminal, and compare runner behavior without leaving the kata.

Open a room → Or join with a code
10Stacks ready to run
Liverunner telemetry
4Isolation modes to compare
The discipline

The loop.

3·phases
01

Red.

Open a room around a failing test. The kata starts in the red phase on purpose, with the runner and result surface already watching.

Driver · defines the next behavior
02

Green.

Write the smallest passing implementation. The room keeps the code, the raw output, and the structured result in one place.

Navigator · keeps the scope honest
03

Refactor.

Then compare what changed, not only in code quality but also in runtime behavior across providers and language stacks.

Both · use the telemetry, not guesswork
What is real today

The baseline.

04·core
01Templates · multi-language

Ten stacks, one flow.

Choose from C#, F#, VB.NET, Python, Rust, Go, Elixir, Jest, and Vitest templates and open the same room pipeline on each.

02Rooms · host-owned

Shared edits, authoritative snapshot.

The host owns the room state, relays edits through SignalR, and now persists room snapshots to disk so the room survives a restart.

03Providers · pluggable

One room, multiple runners.

Switch between process, bubblewrap, nsjail, and docker-runsc without changing the code path the room itself is using.

04Ledger · evidence

Cold and warm runs, preserved.

The host stores a runner experiment ledger so the comparison survives the session instead of vanishing with the terminal output.

torikata. TDD pairing studio
01/03 — Open or join a room Admin ← Home
Step 01 — Open a room

Room for
ritual code.

A TDD pairing studio for developers who train with intent. — Start the room, pick a stack, then move straight into the editor and runner surface.

New room.

01/03
Visibility
Pair mode
Driver rotation

These room settings are visual placeholders for now. The next step already uses the real template catalog and room flow.

Already invited?

Join a room.

Drop the 8-character room code your peer shared. The room opens straight in the editor because the template is already defined by the room creator.

routing

Join jumps directly to the editor route because the room snapshot already exists on the host.

torikata. TDD pairing studio
02/03 — Pick a stack Admin ← Back to room
Step 02 — New room

Pick a stack.

The visual system comes from the prototype. The data comes from the real host template catalog, and opening a card creates a real room.

02/03
0 / 0 templates
Loading templates…
torikata. TDD pairing studio
OPS/ADMIN — rooms and runner logs ← Home
Operations overview

Room fleet
control.

Track live rooms, see active connections, inspect recent execution logs, and clean inactive room snapshots without leaving the host.

01Rooms

0 tracked snapshots

Persisted rooms currently available to load from the host.

02Active rooms

0 rooms with live connections

Derived from the current SignalR room presence registry.

03Connected clients

0 live clients

Anonymous live connections currently attached to rooms.

Loading admin dashboard…

Rooms

Persisted rooms.

Room Stack Files Connected People Created Action
Logs

Recent runs.

Time Room Provider Thermal Outcome Total
torikata.
No room loaded template pending
R
None room
Editor
TEXT Idle —
idle / template pending / room snapshot on host Room not loaded / No file selected