Read through the essays

These fourteen pieces were accessible on the public essay index when this edition was prepared. They give the working methods a voice and a history. The book's new chapters interpret those methods; the original essays keep the claims and limits of their publication.

Three essays are reproduced in this repository. The remaining links open their original public pages. No private drafts or unpublished source notes are included.

Keep the understanding

Outsource the thinking. Keep the understanding. starts with typing and develops the division between high-level intention and low-level movement. It belongs beside Keep the direction and From screen to world.

Meaning above. Motor loop below. makes that interface smaller and more explicit. Software talks to a body. is a short companion note. Both distinguish the protocol and simulation from a finished physical build.

Look at the result

I taught an AI agent to be Player Two follows an independent player, bounded controls, and a failure visible in a screenshot. Read it with The agent loop.

Seeing what a codebase actually does connects a question, a source path, and a bounded experiment. Its historical names remain in the original; the current public tool is System Observatory.

Make the surface useful

When the source goes quiet, the interface should say so. asks what an interface should do with expired information. A surface that refuses. explores the same question through a bounded view. Read them with Honest interfaces.

A small display. A clear contract. gives a display one job and keeps the interesting software elsewhere. Quiet multi-cam beats more cameras. asks when a detection deserves a notification. Both put the person's decision at the center of the interface.

Follow the experiment

A small model and ten pendulums introduces a particular representation-and-control experiment. Seventeen pendulums, one cart follows later work, retained failures, and a public evidence release. Read them with Keep the experiment honest. The original published milestones remain historical, and no independent rerun is claimed here.

Rebuilding a lamp around the hardware on the bench brings mounting, service access, exported geometry, and future physical checks into the same design question. Its upstream design credit and unresolved fit questions matter to the story.

Weekly practice

What a week of building with agents actually looks like connects a game, CAD work, and a software investigation through inspectable results and next checks. It is a useful starting point for the fieldbook as a whole.

Keep Rage Mill moving is a short funding update about sustaining the work. It supplies context about ongoing practice rather than a new technical result.

All source URLs and capture records are in the source catalog.