The Harness
Giving it hands
Files, tools, live systems. What chat alone cannot do, and what changes when the machine can act.
Chat alone reads and writes text. Give the machine hands, file access, a terminal, a browser, an API, and it stops describing work and starts doing it: pulling the real data, running the real check, producing the real file. The moment you notice yourself copying the machine's output into another tool by hand, ask why the machine is not driving that tool itself.
Hands come with a blast radius, so extend them the way you would extend credit. Read access is cheap; grant it freely and the machine stops guessing at your files. Write access is scoped: this folder, this repo, this account. The acts that cannot be undone stay behind the fifth law regardless of how many tools it holds.
How to practice it
Close the copy-paste loop.
If you ferry text between the machine and a tool more than twice, connect the tool. The ferrying was the machine's job.
Read widely, write narrowly.
Default any new capability to read-only. Widen to writes only where you can enumerate what could break.
Feed it the real system.
A connected machine checks the live calendar, the actual spreadsheet, the running service, instead of a stale description of them.
Inventory the hands.
Know what the machine can currently touch. Capability that nobody remembers granting is how surprises happen.