Drop the adapters layer #75

Merged
vnprc merged 1 commit from agent/drop-adapters into master 2026-09-30 23:43:53 +01:00
Member

Owner summary

  • What changes: the adapters/<harness>/ pointer files are deleted from this repo; the README layout and harness sections describe the build-time-generated bootstrap instead.
  • What stays identical: memory.md, every topic file, skills, templates, and hooks — session behavior is unchanged on any machine whose harness bootstrap was regenerated, and each session reads one file fewer.
  • What proves it: a grep across the allod repos finds no remaining adapters/ reference except negative witnesses in the archetypes check (asserting the generated bootstrap contains none) and archived strategy notes; the generated bootstrap names memory.md directly (validated in the archetypes PR).
  • If it is wrong: a session on a not-yet-rebuilt VM hits a missing adapter path — do not merge this before every fleet VM has rebuilt.

Merge gate: merge only after every fleet VM — and each deployment's private-fork VMs — has rebuilt on the new archetypes pin. Handoff for each deployment: delete its private memory fork's adapters/ layer the same way (git rm, drop the README adapter section) once its profiles rebuild; the claude attribution-ban policy now lives in the archetypes generator's Claude template.

Risk

R1 given the merge-order gate — deleting files nothing reads any more; rollback is a revert. Merging early is the one failure mode, and the gate above is its whole defence.

Validation

grep -rn "adapters/" across allod/tools, allod/vm, allod/nexus, allod/deploy, allod/profiles, allod/inventory, and the archetypes branch: no hits outside checks/pi-integration.nix negative witnesses and allod/strategy/archive history. No references remain in this repo.

Closes allod/archetypes#123

## Owner summary - What changes: the `adapters/<harness>/` pointer files are deleted from this repo; the README layout and harness sections describe the build-time-generated bootstrap instead. - What stays identical: `memory.md`, every topic file, skills, templates, and hooks — session behavior is unchanged on any machine whose harness bootstrap was regenerated, and each session reads one file fewer. - What proves it: a grep across the allod repos finds no remaining `adapters/` reference except negative witnesses in the archetypes check (asserting the generated bootstrap contains none) and archived strategy notes; the generated bootstrap names `memory.md` directly (validated in the archetypes PR). - If it is wrong: a session on a not-yet-rebuilt VM hits a missing adapter path — do not merge this before every fleet VM has rebuilt. **Merge gate: merge only after every fleet VM — and each deployment's private-fork VMs — has rebuilt on the new archetypes pin.** Handoff for each deployment: delete its private memory fork's `adapters/` layer the same way (git rm, drop the README adapter section) once its profiles rebuild; the claude attribution-ban policy now lives in the archetypes generator's Claude template. ## Risk R1 given the merge-order gate — deleting files nothing reads any more; rollback is a revert. Merging early is the one failure mode, and the gate above is its whole defence. ## Validation `grep -rn "adapters/"` across `allod/tools`, `allod/vm`, `allod/nexus`, `allod/deploy`, `allod/profiles`, `allod/inventory`, and the archetypes branch: no hits outside `checks/pi-integration.nix` negative witnesses and `allod/strategy/archive` history. No references remain in this repo. Closes allod/archetypes#123
Harness bootstraps are generated at VM build time by the allod/archetypes
home-manager module and name memory.md directly.

Refs allod/archetypes#123
vnprc force-pushed agent/drop-adapters from fd3050170c to 729b8c89a1 2026-09-30 23:26:28 +01:00 Compare
vnprc merged commit 729b8c89a1 into master 2026-09-30 23:43:53 +01:00
vnprc deleted branch agent/drop-adapters 2026-09-30 23:43:53 +01:00
Sign in to join this conversation.
No description provided.