Migrate, external-content intake and classification

Contents: Ideal State · Anti-criteria · Inputs · Tool contract · Output format · Gotchas · Examples · References · Data & Config

Migrate intakes external content, classifies each chunk against the LifeOS taxonomy, and commits it to the right destination with provenance. New LifeOS users usually arrive with years of notes (a CLAUDE.md, a markdown vault, journal dumps, rules from another tool) that map onto no LifeOS structure, and sorting hundreds of chunks by hand never gets done. Migrate proposes a destination for every chunk with a confidence score: high-confidence chunks auto-approve, medium ones ask for confirmation, low ones get a walk-through. Unlike /interview, which asks questions to fill gaps, /migrate already has the content and only classifies and routes it.

Ideal State

• Every committed chunk lands in a LifeOS destination that fits it and carries provenance: an HTML comment naming source file, section and timestamp.
• The principal sees the whole routing proposal (chunks per target, average confidence, UNCLEAR and under-40% counts) before anything is written, and picks how to approve it.
• Each chunk under 60% confidence is approved one at a time, each UNCLEAR chunk is routed by the principal's own call, and each chunk under 40% is walked through with them first (a conversational rule; the tool does not enforce the 40% line).
• Every AI collaboration rule reaches a constitutional surface (a CLAUDE.md operational rule, a hook, a settings.json permission, or the relevant skill's Gotchas), and every knowledge chunk becomes a new typed note with source metadata.
• The run closes with what was committed per target, what is still UNCLEAR, and whether /interview should fill what the migration left sparse.

Anti-criteria