What problem does it solve? Adopting a structured personal knowledge system means inheriting years of accumulated notes, rule files, and vault exports that were never shaped to its taxonomy. Manually sorting hundreds of chunks into the right destinations is tedious enough that the old material usually sits unused. ## Core Features & Use Cases - Multi-source intake: Accepts .md/.txt files, directories, stdin, other DevOS installs, CLAUDE.md, Cursor rules, OpenAI Custom Instructions, and Obsidian/Notion/Apple Notes exports. - Confidence-based routing: MigrateScan classifies each chunk into TELOS, IDEAL_STATE, preference, identity, or knowledge targets; confidence ≥70% auto-approves, 40-70% asks for confirmation, and <40% requires a walk-through. - Provenance-stamped commits: MigrateApprove commits approved chunks with source file, section, and timestamp metadata, with fast-path, per-category, and per-chunk review modes. - Use Case: Point it at an old CLAUDE.md or Obsidian vault and get a routing table showing how many chunks land in each destination, then bulk-approve the confident ones and walk through the unclear remainder. ## Quick Start Ask the agent to run /migrate on a file or directory such as an old CLAUDE.md or notes export and approve the proposed routing table.