Research 029: the agent configured through its module, as a plugin the mesh serves #85

Merged
mesh-admin merged 4 commits from research/029-the-agent-configured-through-its-module into main 2026-10-05 08:01:17 +00:00
Contributor

Reopened: the forge's database was restored to an older state after issue 241, and the original pull request (#372) was lost; the branch is intact.

Research 029: everything configurable about the agent through the agent module's tools, as a plugin the mesh serves, at three scopes (mesh, node, home). 01 evidence from four machines; 02 what the vendor allows, with sources; 03 options; 04 the checks tried on one workstation (plugin route confirmed; autoMode from managed settings very likely; the agent cannot undo its own managed settings).

Reopened: the forge's database was restored to an older state after issue 241, and the original pull request (#372) was lost; the branch is intact. Research 029: everything configurable about the agent through the agent module's tools, as a plugin the mesh serves, at three scopes (mesh, node, home). 01 evidence from four machines; 02 what the vendor allows, with sources; 03 options; 04 the checks tried on one workstation (plugin route confirmed; autoMode from managed settings very likely; the agent cannot undo its own managed settings).
mesh-admin added 4 commits 2026-10-05 07:59:47 +00:00
Skills, subagents and hooks have no machine-wide place but a plugin, and
hand-copied homes have drifted and gone stale on every machine. Records the
evidence, what the vendor allows, and the options a decision must settle.
The operator's direction: mesh, node and home. A plugin carries the first
two; the home scope places items the module owns path by path; instructions
follow the same layering.
Six of seven checks confirmed and autoMode from managed settings very likely;
the agent cannot undo its own managed settings, which a design must allow for.
mesh-admin merged commit 85c6db0600 into main 2026-10-05 08:01:17 +00:00
mesh-admin deleted branch research/029-the-agent-configured-through-its-module 2026-10-05 08:01:17 +00:00
Author
Contributor

Delivery novox/hq@85c6db06004f — held since 2026-10-06T23:05:28Z

Held for a person: merged without a passing check: only a person decides that it goes on — mesh-delivery.release with why lets it go on.

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

  • 2026-10-06 23:05 (new) → proposed (announced): novox/hq#85 merged; its head was not heard by this owner, so it is made from the forge's word
  • 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/hq@85c6db06004f` — **held** since 2026-10-06T23:05:28Z Held for a person: merged without a passing check: only a person decides that it goes on — `mesh-delivery.release` with why lets it go on. **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/hq#85 merged; its head was not heard by this owner, so it is made from the forge's word - 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#85