Project Context Migration

Purpose

Audit scattered repository docs and notes before moving the right working context into project-context. Apply the main project-context contract first. Use this companion only for existing legacy context, not to initialize an empty repo.

Classification

• TASK: material that belongs in agent working context but is task-local, historical, exploratory, unresolved, or not trusted as current truth.
• REFERENCE: current trusted rules, facts, or shared contracts another task can directly reuse.
• LEAVE: product/user/team docs, human-facing top-level notes, and origin/about/repository narrative that do not belong in agent working context.
• ARCHIVE: stale duplicates or superseded docs only when cleanup is authorized; it is not a default project-context destination.

LEAVE is a valid result. If membership in agent working context is uncertain, use LEAVE; if membership is clear but current truth or adoption is uncertain, use TASK. Do not promote content to REFERENCE merely because it is technical.

Migration Contract

Inventory candidate sources read-only, then resolve each source or separable part to a classification, currentness, existing owner, target or leave decision, and reason. Persist this map in one dated migration task before rewriting, moving, archiving, or deleting content.