delegate-impl dispatches workers through 'allod change run'; worktree conventions become clones #86

Closed
opened 2026-10-20 06:05:48 +01:00 by vnprc-agent · 6 comments
Contributor

The delegate-impl skill dispatches every worker through allod change run, and the worktree conventions describe clones, so an overseer reading the skill cold runs a swarm the sandboxed way without being told.

Part of allod/strategy#69. This is the closing child: its PR carries Closes allod/strategy#69 and lands after the allod/tools command exists.

Primary goals:

  • Dispatch is sandboxed by default — skills/delegate-impl/SKILL.md: a worker runs under allod change run; it commits on its branch and never pushes; the overseer pushes with record after verification and never authors a commit; the swarm size is the VM's memory divided by the per-worker cap.
  • Worktrees are clones — git-workflow.md, Worktrees and Concurrent Agents: a tree under ~/changes is a self-contained clone the parent ledgers; the silent-collision warning narrows to unsandboxed sessions; the cleanup hazard in allod/tools#127 is noted as closed by the ledger if the tools PR closes it.
  • allod.md Workspace Tools — one line for allod change run.

Scope

In: the three files named. Out: the tools and archetypes halves.

The `delegate-impl` skill dispatches every worker through `allod change run`, and the worktree conventions describe clones, so an overseer reading the skill cold runs a swarm the sandboxed way without being told. Part of allod/strategy#69. This is the closing child: its PR carries `Closes allod/strategy#69` and lands after the `allod/tools` command exists. Primary goals: - **Dispatch is sandboxed by default** — `skills/delegate-impl/SKILL.md`: a worker runs under `allod change run`; it commits on its branch and never pushes; the overseer pushes with `record` after verification and never authors a commit; the swarm size is the VM's memory divided by the per-worker cap. - **Worktrees are clones** — `git-workflow.md`, Worktrees and Concurrent Agents: a tree under `~/changes` is a self-contained clone the parent ledgers; the silent-collision warning narrows to unsandboxed sessions; the cleanup hazard in `allod/tools#127` is noted as closed by the ledger if the tools PR closes it. - **`allod.md` Workspace Tools** — one line for `allod change run`. ### Scope In: the three files named. Out: the tools and archetypes halves.
Author
Contributor

Handoff: three commits on agent/sandboxed-dispatch, budget hook green; PR body (this PR closes allod/strategy#69):

An overseer reading the delegate-impl skill cold now runs workers the sandboxed way: it makes each worker a clone with allod change begin -d, dispatches it through allod change run, and pushes with record after verification without ever authoring a commit. The worktree conventions and the workspace tool list describe clones and the parent's ledger instead of linked worktrees. Nothing changes on any machine; this is memory text. Proof is a read against the landed allod change usage text and .hooks/memory-budget --worktree passing. If it is wrong, revert; the tools change it describes stays usable from its own docs.

Refs allod/strategy#69. Closes allod/memory#86. Closes allod/strategy#69.

Risk

R0. Memory text only; no runtime, generated or operational behaviour.

Validation

  • Wording diffed against changeUsageText and docs/allod-change-run.md on the allod/tools branch for allod/tools#282; no drift.
  • .hooks/memory-budget --worktree: exit 0.
Handoff: three commits on `agent/sandboxed-dispatch`, budget hook green; PR body (this PR closes allod/strategy#69): An overseer reading the delegate-impl skill cold now runs workers the sandboxed way: it makes each worker a clone with `allod change begin -d`, dispatches it through `allod change run`, and pushes with `record` after verification without ever authoring a commit. The worktree conventions and the workspace tool list describe clones and the parent's ledger instead of linked worktrees. Nothing changes on any machine; this is memory text. Proof is a read against the landed `allod change` usage text and `.hooks/memory-budget --worktree` passing. If it is wrong, revert; the tools change it describes stays usable from its own docs. Refs allod/strategy#69. Closes allod/memory#86. Closes allod/strategy#69. ## Risk R0. Memory text only; no runtime, generated or operational behaviour. ## Validation - Wording diffed against `changeUsageText` and `docs/allod-change-run.md` on the `allod/tools` branch for allod/tools#282; no drift. - `.hooks/memory-budget --worktree`: exit 0.
Author
Contributor

Handoff update: the branch now carries five commits, rebased onto current master (one conflict in skills/delegate-impl/SKILL.md resolved keeping both the verify-merge pointer and the sandbox facts); it also documents the trusted-user prerequisite (allod/vm#12), the config-safety gate, the tracked-hooks rule and the cleared environment. PR body unchanged except that it closes allod/strategy#69 only after allod/tools#282 and allod/vm#12 land.

Handoff update: the branch now carries five commits, rebased onto current master (one conflict in skills/delegate-impl/SKILL.md resolved keeping both the verify-merge pointer and the sandbox facts); it also documents the trusted-user prerequisite (allod/vm#12), the config-safety gate, the tracked-hooks rule and the cleared environment. PR body unchanged except that it closes allod/strategy#69 only after allod/tools#282 and allod/vm#12 land.
Author
Contributor

Handoff update: local agent/sandboxed-dispatch is clean and unpushed at 469ba97 (seven commits on current master). The prior PR body still describes the intended behavior; use this current head and validation. The three changed files now match the finalized allod/tools command at cd9a968: sandboxed dispatch, cloned change trees, ledger locking, trusted-user refusal, host-side Git isolation, and clone-path patch relay. In particular, a relay from ~/changes names that clone's path; a registry ID would read the source machine's shared checkout instead.

The memory budget hook and git diff --check origin/master...HEAD pass. This is R0 text only. Land this after allod/tools#282, allod/archetypes#146, and the paired allod/vm#12 plus allod/nexus change, so the skill describes a usable deployed command.

Refs allod/strategy#69. Closes allod/memory#86. Closes allod/strategy#69 after the prerequisites above land.

Handoff update: local `agent/sandboxed-dispatch` is clean and unpushed at `469ba97` (seven commits on current master). The prior PR body still describes the intended behavior; use this current head and validation. The three changed files now match the finalized `allod/tools` command at `cd9a968`: sandboxed dispatch, cloned change trees, ledger locking, trusted-user refusal, host-side Git isolation, and clone-path patch relay. In particular, a relay from `~/changes` names that clone's path; a registry ID would read the source machine's shared checkout instead. The memory budget hook and `git diff --check origin/master...HEAD` pass. This is R0 text only. Land this after `allod/tools#282`, `allod/archetypes#146`, and the paired `allod/vm#12` plus `allod/nexus` change, so the skill describes a usable deployed command. Refs allod/strategy#69. Closes allod/memory#86. Closes allod/strategy#69 after the prerequisites above land.
Author
Contributor

Handoff, final: head b2689d0 on agent/sandboxed-dispatch, seven commits rebased onto current master 1bf62f1, budget hook green. Lands last; closes allod/strategy#69.

Handoff, final: head `b2689d0` on `agent/sandboxed-dispatch`, seven commits rebased onto current master `1bf62f1`, budget hook green. Lands last; closes allod/strategy#69.
Author
Contributor

Shipped to relay: head 8448b05, squashed to two commits (delegate-impl; conventions), tree byte-identical to the verified head, budget hook green.

Shipped to relay: head `8448b05`, squashed to two commits (delegate-impl; conventions), tree byte-identical to the verified head, budget hook green.
Author
Contributor

Landed on master.

Landed on master.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
allod/memory#86
No description provided.