Interactive mockup · Code Raven · 6 September 2026
Interactive mockup · Code Raven · 6 September 2026

Feature Lab — The Bench

One persistent surface organised around materials and the relations between them. Working prototype — the gestures below actually run.

Drag a pale item → tear it into the bench Drag a fragment onto another → draw a relation Type on the line, Enter → resolves both Click a written line → press Click a seam → tear back

Mira answers your move, not a clock. Every time you write on a relation she draws one line — never a fragment — reaching to something you built in another project. Three lines maximum, then she stops.

A fragment is a name plus a line of what it does. A bare label sparks nothing — "plan dormancy tier" is a subsystem, not an idea you can relate to another idea. The seed material here is read straight from this project's Features layer, name and first line of description together, which is what makes two fragments comparable at a glance. The exporter has to carry the description, not just the title.
The rule the prototype enforces. Press only works on a relation. There is no press-on-a-fragment and no press-on-a-pile, so the comparison is always the precondition and the lever can never substitute for the work it depends on. Try clicking a fragment directly — nothing happens, by design.

The four states

Three values and one texture channel, so wear never competes with contrast for the same reading. Drag a fragment around four or five times in the bench above and it picks up wear live.

Guide week gating
Dormant
Never passed through your hands. Outside the resolution system. Flat, no shadow, no torn edge.
Routing is the actual problem
Unresolved
Torn by you, nothing attached, nothing done to it. Full contrast indefinitely.
Move to Project already exists
Resolved
Pressed, or connected by a line you wrote on. Recedes. Avoidance is not resolution, so what you keep walking past stays dark.
Routing is the actual problem
Worn
Repeatedly handled. Creases and thinned patches at full ink — a texture, not a fourth grey.
Changed from the room's answer. Game Feel Expert specified wear as a rendering plane alongside three contrast states, which puts four values on one axis. Wear reads better as physical handling laid over full contrast. Value carries resolution; texture carries history.

Deliberately absent

Still open