jschoubben
c0b35652d0
papa-hq reads 01 research -> 03 decision -> 02 design. The order is a scar, not a choice: 02-DESIGN existed from its initial commit, and when adr/ was finally promoted on 2026-07-13 it took the next free number rather than its place in the sequence. By then design was too settled to renumber. hal-hq was three commits old, so it is not. adr/ becomes 02-DECISIONS and 02-DESIGN becomes 03-DESIGN, and following the folder numbers now walks the process in the order it happens: research produces a decision, the decision authorises a design. 00-GENESIS becomes 00-META, matching papa's rename from the same restructure. Every path reference rewritten across documents, frontmatter, playbooks and skills. All links resolve; all 58 frontmatter blocks parse and their path fields still point at files that exist.
1.7 KiB
status, updated
| status | updated |
|---|---|
| canonical | 2026-08-22 |
Effect
Imagine the mesh works as intended. What is different?
You ask, and it happens
An agent says what it wants — from a terminal, a phone, a message — and the mesh takes it from there. It works out which nodes are involved, does the work, and returns a result. Nobody opens a console, recalls which node holds what, or follows a runbook written months ago.
The interface is intent. The mesh handles the rest.
The nodes look after themselves
Updates land, services recover, disks are kept clear, certificates renew, and the mesh notices when something is wrong before you do. Maintenance stops being a thing you schedule and becomes a thing that has already happened.
When something genuinely needs a decision, you are asked — with the context, not a log line.
Work continues while nobody is watching
Agents keep working overnight and across the week. What they did is legible afterwards because it is all in one record: what was asked, what was decided, what changed. The overnight work can be trusted, which is what makes it worth doing at all.
The mesh remembers
Nothing has to be explained twice. What was learned — how a thing works, why a decision went the way it did, what broke last time — is available to whoever needs it next, whether that is an agent working at 4am or a human agent six months later.
A human agent's environment is part of it
The node a human agent sits at is not outside the mesh looking in. The desktop, the notifications, the shell are how that agent acts — maintained by the mesh, exactly as a spawned session is for an agent that is not human.
The difference for a human agent
Less time spent operating the mesh. More time spent deciding what it should do.