September 7, 2026
A harness is an environment that builds, tests, and maintains its own reusable skills. The definition, the one rule that holds it together, and a single question that finds yours.
A harness is an environment that builds, tests, and maintains its own reusable skills.
Work you do once becomes work the system does again without being asked twice.
That is the definition. The rest is detail, and this page is where the definition lives, so every session that uses the word can point here.
What sits outside it
A folder of prompts you paste from builds nothing and maintains nothing. You still do the remembering.
A subscription is a bill.
A harness is the layer between you and the tool where your decisions get written down once and stop being decisions.
The rule that holds it together
The line comes from Israel Ayliffe, who runs our Harness Engineering series:
"The system may analyze on its own and recommend on its own, but it may only change the harness after a human says yes."
Analysis is free. Recommendation is free. Changing itself takes a person.
With that line in place, you get something you can hand to somebody else and explain in a sentence. Leave it out and the setup rewrites its own rules quietly, and you can no longer vouch for what it does.
How to find yours
You do not need a blank page. You have been writing the specification for a month already.
Thirty days of your actual work is a better document than anything you would draft on day one, because it records what you did.
Open whichever tool you use most and ask it this, exactly:
"Based on everything you know about how I work, what are the three things I keep asking you to do that should have been set up once and never asked again?"
That list is the beginning of a harness.
Keep it open
A harness earns its keep when someone opens it again. Read it every couple of weeks. Cut what nobody remembers writing. Keep the standards. We wrote up what that looked like on our own setup here.
It goes faster with other people watching and asking, building out loud, which is how the Harness Engineering sessions run. A plain version of how we write the pages for those sessions is here.
Everything on the calendar: https://luma.com/TheHouseofCuriosity
