jochen
a28da1734b
ADR 0244 sorts the mesh's concepts into ten domains (ADR 0006's contexts carry over as domains), keeps machine and node as distinct words, and makes the glossary the authority with every retired word on its replacement's Not: line. To-be 49 draws the domains; the glossary is reorganised by them, its two contradictions removed and the missing words added. words.py now fails on a retired word in running prose and on a word defined twice, so the rule is enforced rather than believed; the 63 documents it failed on are reworded here, and research 034 is kept as the record of the words it studied.
49 lines
1.7 KiB
Markdown
49 lines
1.7 KiB
Markdown
---
|
|
status: canonical
|
|
updated: 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 terminal, 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.
|