For engineering

From an intention to a reviewed design.

The part, the board, the bill of materials and the simulation live in one project folder — and agents plan the work with you, in the open.

A machined aluminium bracket standing on its drawing on a drafting table.

Plate 10 · An aluminium bracket beside its drawing, on a drafting table at first light

Agents plan in the project's own registers.

Plan

A project is a folder with a project.json that holds its registers: requirements, assumptions, open questions, decisions and verification. Agents read them, add to them and work against them — so the reasoning behind a design is a file you can review, not a chat you have to scroll.

The example project takes one sentence — make ten 5 V LED indicator boards — to a reviewed draft: schematic, board, BOM and checks.

Design in 3D. Or design in code.

The 3D app models parts with a history you can edit, and imports STEP, IGES, STL, GLB, OBJ, 3MF and more. Prefer code? Write parts in TypeScript, JSCAD, replicad or CadQuery-style Python and evaluate them in a sandbox.

A 3D-printed part on a desk in front of a monitor showing its wireframe.

Plate 11 · A part's operation graph, and the part it builds

A small circuit board with a row of LEDs seen through a loupe.

Plate 12 · A two-layer board under a loupe

Electronics

A schematic and its board are two files.

board.sch.tsx and board.pcb.tsx are code, and the board names its schematic — cross-probing works, and each stays a readable file. KiCad goes in and comes out.

The built-in generator knows a bounded set of circuits. Ask it for something outside that set and it says no, rather than drawing a different circuit that merely looks right.

The BOM is a spreadsheet. A real one.

Bill of materials

Open bom.xlsx in the sheets app, edit it beside the design, and export it back to Excel for your supplier. No proprietary parts database between you and the numbers.

Fail in simulation, as often as you like.

One simulation format covers rigid bodies, fields, particles and more, running in your browser. Trial files sweep a parameter across many runs and record each one. Drag a body with your mouse and the force is recorded too.

A simulated result is always labelled simulated. It never counts as physical evidence.

Ghosted trails of one object falling and bouncing, many times over.

Plate 13 · A trial sweep: forty runs of one reach, overlaid

An opened parts box with bagged fasteners beside a machined part.

Plate 14 · A supplier's reply, filed beside the part it is about

Partners

Coordinate with the people who build it.

Agents can write to suppliers and partners through your mailbox, Slack, Teams or Discord — under an outreach grant that limits who and how often, with every message recorded before it is sent.

Replies still come to you. Purchasing stays a decision you make.

Watch the whole job on one screen.

Oversight

Dashboards are files too: a 3D view, the BOM, the run log and an agent's thread, arranged once and opened with one click. Everything the agents did is in the project's runs, in order, with who did it.

Start with the example.

The LED-indicator example ships with the workbench: the schematic, the board, the BOM and the decisions behind them, ready to read.