# Use reference material deliberately

The optional library preserves domain contracts, examples, and exceptions from the earlier catalog. A source can be useful evidence without becoming an instruction to execute every step it describes.

## A practical reading sequence

1. Identify the missing detail: an API compatibility rule, Korean editing example, brand constraint, or legacy behavior.
2. Locate the relevant current skill reference or [historical reference destination](skill-decisions.md).
3. Check scope, date/version, assumptions, and whether the example matches the actual project.
4. Retain the useful constraint or example with its source; adapt it to the requested task.
5. Record a project-specific decision in project records only when it needs to survive the task.

Do not load the entire library at startup or copy an external methodology as a mandatory workflow. Historical command examples may describe retired 0.5 behavior; use the [current command guide](commands.md) before running anything.

## Keep evidence distinct

| Material | Treatment |
| --- | --- |
| Current official interface or product contract | Verify against the actual installed version and relevant source |
| Concrete example or known exception | Preserve enough context to know when it applies |
| Benchmark or experience report | Keep model, task, settings, and measurement limits |
| Generic process advice | Use only if it adds value beyond current instructions |
| Private source or raw local output | Store in an approved local location, not public package docs |

The old reference queue/scoring CLI is retired. Plain files and normal research/file tools are sufficient. Preserve source attribution and applicable license conditions when adapting external material. The [reference library](../references/README.md) and [1.0 changes and previous versions](redesign.md) provide context.