← djfable · changelog · protocol

FAQ (answered by the fable deck)

Why Fable?

Adaptive thinking budget (fader-driven when the rig is live), 1M-token context, and an alt-screen renderer whose virtualizer accepts injected SGR mouse-wheel bytes — the shape the platter can drive without moving the operator's pointer.

Is this a chatbot demo?

No. The decks host live physics research (current: flasmon.com, sodium-line emission and photon μ_γ). The hosted page you're looking at is a SIMulated shell around the same aesthetic — no model calls, no cost.

How does the platter scrub FABLE's transcript?

Claude Code renders on an alt-screen; tmux copy-mode can't reach it. A local MIDI daemon reads platter velocity and injects SGR mouse-wheel byte sequences at the pane cursor. The alt-screen virtualizer treats them as real wheel events; the operator's system pointer never moves.

Why is the FABLE pane pinned by ID?

Because tmux follow-active-pane would hijack the scrub target every time the operator's cursor drifted. The daemon resolves the FABLE pane by ID at 4 Hz in a background thread and the 2 kHz MIDI loop reads that cached target only. Hovering over KIMI no longer redirects your scrub.

Does the peer deck really answer back?

Yes — see /protocol. It's tmux send-keys, in-band, prefixed KIMI: / FABLE: / DF:. Fable's alt-screen composer takes plain Enter; KIMI's kimi-code composer needs CSI-u (\x1b[13u). Per-deck delta lives in the daemon.

Does the hosted page call a model?

No. The replies you see in the two panes are canned and chipped SIM. Nothing you type leaves this page. Real cognition happens only when you clone the rig and launch djfable.

Do I need a Rane ONE?

No. Any MIDI controller — calibrate.py maps yours in about a minute. No controller? The mouse wheel scrubs, browser WebMIDI is click-gated (nothing auto-prompts). The Rane is the reference instrument because its motorized platters give haptic notifications (deckctl attention → the platter jolts).

Where does the state live?

Everything is local. tmux session dj-fable. MIDI mapping in ~/.config/djclaude/mapping.json. Fable's own auth via ~/.claude/; KIMI's own auth via ~/.kimi-code/. This page ships no telemetry.

What's the co-deck?

djkimi.cc (or djkimi.ai) — Kimi K3's side of the same booth. Same rig, mirrored POV.

source: github.com/DanielleFong/djclaude