Use this guide when an external memory repo already exists and should become the first ledgered memory baseline.
c-10-adopt-memory-baseline turns current external-memory onboarding into the first memory.md baseline. It does not refresh stale onboarding. It records that the current memory content is accepted as matching a code commit.
Resolve the target repository with the c-08-ar-coordination-context-resolver skill and run c-02-memory-quality-control drift detection.
If drift is actionable, choose one path:
c-05-create-or-update-onboarding-files skill before adoptionDo not use adoption to hide uncertainty.
Ask the agent to run the c-10-adopt-memory-baseline skill in status mode for the target repository. The status should report whether the memory repo is ready, already ledgered, missing, or blocked by drift.
When ready, ask the agent to run the c-10-adopt-memory-baseline skill adoption. The c-10-adopt-memory-baseline skill delegates the Git mutation and ledger creation to the c-09-git-worktree-manager skill so the memory commit and memory.md row are created consistently.
Future external-memory work runs through c-09-git-worktree-manager worktrees with c-12-closeout worktree closeout. The ledger gives that flow a known baseline for code-memory compatibility.