# Adaptation Checklist

Use this when another user wants to adopt the skill in a different vault.

## Customize First

- vault root path
- raw folder names
- output folder names
- whether root loose notes should be auto-moved
- whether a compile or staging layer exists
- preferred formal page categories
- domain names

## Verify These Files Exist

- governance file such as `CLAUDE.md`
- `wiki/index.md`
- `wiki/log.md`
- at least one maintenance instruction file or skill

## Make These Decisions Explicit

- what counts as raw
- what counts as output
- what can be promoted into formal knowledge
- whether principles are first-class pages
- where loose root notes should go
- whether query outputs should always be saved or only saved selectively

## Good Defaults

- keep raw read-only by default
- keep outputs out of the formal wiki by default
- use source pages as the bridge
- make questions, methods, and decisions the main axis
- add principles when the user needs stronger "why" and "theory" support
- treat outputs as reusable query artifacts and future write-back sources