c-10-adopt-memory-baseline

To adopt external onboarding as a memory baseline, the Skill validates existing content, resolves context drift, and requires explicit acceptance before creating memory.md mapped to the current code HEAD.

Memory drift evaluation checks whether external onboarding content is current before adoption. You need it when bootstrapping a memory baseline to ensure your initial ledger is trustworthy and not outdated.

Yes, you can run a dry-run to preview memory baseline adoption. This allows you to review the proposed memory.md mapping and drift evaluation results before explicitly accepting and applying the changes.

Yes, the git-worktree manager maps validated external onboarding content to memory.md. This coordination establishes the initial memory ledger tied to your repository's current HEAD after drift is accepted.

Adopting a memory baseline without explicit drift acceptance bypasses the quality-control process, risking an untrustworthy ledger. The Skill enforces explicit gating to prevent adopting unproven or outdated onboarding content.

The best way to bootstrap a memory ledger is validating external onboarding docs through drift checks, using a dry-run preview, and securing explicit acceptance before mapping the content to memory.md via git-worktree.