An interface you can only operate with a mouse is one you haven’t finished.
Interaction proofs. Every one works without a pointer, and each names the rule it obeys.
Proof 01A shortcut announces itself, and never steals.
What the keyboard actually sends
key is what the layout produced. code is which physical switch closed. On a French keyboard the key labelled A reports key: "q" and code: "KeyA", so a shortcut bound to one of them moves when someone changes layout and the other one stays put. Terminal emulators care about this at protocol depth. There is nothing here to click.
Tab to this panel, then press any key. Tap here, or the button below, to bring up your keyboard.
Tab and Escape are never intercepted; they are how you leave. The arrows, Space, Home, End and PageUp/Down are intercepted while this panel has focus, because otherwise the page scrolls out from under you.
The other proofs
- Proof 02A chord that announces itself, and gives the keyboard back
A tmux-style prefix: visible pending state, a timeout that says so, an escape hatch.
A shortcut announces itself, and never steals.
- Proof 03A hundred thousand lines that still scroll at frame rate
Virtualized scrollback with the worst frame on screen — and a switch that turns the virtualization off.
It holds frame rate when the data stops cooperating.
More are being built, one at a time.
Explainers
Or: things explained by letting you break them.
Exhibits with dials rather than diagrams — why consensus breaks at exactly one third, and why most Sui transactions never wait in line. The Lab is how I build; this is how I explain.
Open the explainers