M.

The workbench

Think by making.

Small experiments that run in your browser. Pick one. It opens here, on the bench.

Bench 01 / Beneath the interface

How software runs.

Scheduling, compiled code, and search, one small view at a time.

Bench 02 / Many hands

Building together.

People and AI change one piece of work. Watch the work stay whole.

Main movesone merge at a time, tests twice
Bench 02 / Many hands

Main moves

Three agents ask to merge. A queue takes one at a time, runs the tests twice, and moves the other work onto the new main.

Simulation / a made-up repository
  • Agent Aworking on m0

    Add a currency to formatPrice

    src/products.js and its tests

  • Agent Bworking on m0

    Show the old price on sale books

    src/render.js 58–64, and a new test that expects "$24.00"

  • Agent Cworking on m0

    Round the buttons

    src/styles.js 30–40

People do not fix merge conflicts. gitring README

Queue

The queue is empty.

Merge ticket

  1. Merge
  2. Tests on the work copy
  3. Tests on main plus the work
  4. Commit with a note

Ask an agent to merge. Then press Next step.

Log

Nothing happened yet.

What this shows
One merge at a time keeps main whole. Tests run on the work copy and again on main plus the work. When main moves, the other work moves with it.
Honest note
The steps follow gitring's merge order and redo policy. The agents, the files, and the test results are scripted.
Related: gitring Next on the bench: Line and length
Back to the bench ↑

Bench 03 / Things in motion

A ball and an arm.

A cricket delivery and a robot arm. Each one moves by a small rule.

Field notes

The experiments run locally in your browser.
Small enough to inspect.