ONE SYSTEM. EVERY VIEW.
The schematic, the physical representation, the measurements, the evidence and the replay all refer to the same semantic system. Select TP_3V3 anywhere — it is TP_3V3 everywhere.
INFRASTRUCTURE FOR PHYSICAL ENGINEERING WORK
Physical engineering work disappears across instruments, logs, hardware and conversations.
BenchTape turns that work into an executable, replayable, verifiable engineering trace.
WORLD / OPENMANIPULATOR-X · PHYSICAL · SOURCE-BACKEDTHE PRODUCT
Inspect the physical system, operate it, measure it, reason about what happened — without leaving the engineering context.


BenchTape keeps the system, the actions, the evidence and the reasoning in one continuous engineering record.
Start with a source-backed model of the physical system — its components, connections, capabilities and known state.
The system becomes the shared context for the work.

The schematic, the physical representation, the measurements, the evidence and the replay all refer to the same semantic system. Select TP_3V3 anywhere — it is TP_3V3 everywhere.
THE PROBLEM
Software teams have commits, traces, tests, logs and reproducible environments. Physical engineering work spans schematics, instruments, screenshots, notebooks, hardware, chat, tribal knowledge and AI conversations.
The final answer may be recorded. The process that produced it often isn't.
A Tape preserves the operations, measurements, evidence and decisions that produced an engineering outcome — in order, against the exact system state they came from.

SEALED · VERIFIED ✓
Kelvin reasons over the work already captured in BenchTape. It can suggest what to inspect next, but Runtime and evidence remain authoritative.
“I can't find a 9 V input reading in this session's record… The only recent measurement is DMM_1 on TP_3V3 at 3.31 V, which is inside the 3.20–3.40 V target.”
real captured turn · production dataAdvice consistent with the recorded work is accepted into the trace.
Proposed guidance not supported by the evidence in the session is refused. Evidence and Runtime remain authoritative.
The World stays reusable, the Challenge stays reusable, every attempt is isolated, and each run leaves its own Tape.
Give an engineer the system and see how they actually work.
Four applications of the same system — not four products.
Electronics is the initial domain because measurement-based reasoning is highly observable. The underlying World model is built around components, capabilities, ports, state, operations, measurements and spatial identity — the abstraction is physical systems, not a single discipline.
SEE THE PUBLISHED WORLDS →Open a World. Run a Challenge. See how the work becomes inspectable.