OR-1 listens while you think out loud and, every time you say "or," splits your note into visible branches — each one auto-titled so you can read the map at a glance, so the alternatives, the dead ends, and the reasoning stay on the canvas, and any decision can be traced back through every node that led to it.
okay now help me write a heading for this
No Figma file — just notepad sketches, reference photos of real tape recorders, and design done directly in the running app: describe the component, review a mock, correct it, ship the spec to a coding agent. Every screenshot became the next iteration's reference.
.gif)
.jpg)
The image on the left is what a spoken sales deal review looks like in OR-1: five forks contract, incentive, champion, format, timing ending in one decision. The rejected discount is still on the canvas with the reason it died. That's the handoff: not a summary, the whole conversation.
