jschoubben
cf9357e8e9
What the mesh is, what it is becoming, and why. Implementation lives in the code repositories; the reasoning lives here. 00-GENESIS mission, engineering context, effect, and the rules that hold 01-RESEARCH investigations, before they harden into design 02-DESIGN the authoritative specification adr numbered decisions — what was chosen, and what was rejected DECISIONS.md the ledger: every decision, in the order it was taken Written for a reader who is not its author and has no access to the mesh it describes. Addresses use the documentation ranges of RFC 5737 and RFC 1918; nodes are named by role. Single initial commit by intent. The prior history came from a private repository and carried operational detail — a routable address identified as a VPN hub, real domain names, a hosting provider — which sanitising a tip commit would not have removed from the log.
1.7 KiB
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.