What problem does it solve? Teams moving off an mma-based workflow need their accumulated history — journal lessons, specs, plans, audits — preserved on the ZZ platform without losing provenance or falsely stamping unapproved historical documents as gated, approved work. ## Core Features & Use Cases - Journal-to-knowledge migration: Converts .mma/journal/nodes/*.md into ZZ knowledge nodes, preserving the six shared node types, tags, and supersede edges. - Historical archive as sources: Imports specs, plans, explorations, audits, and other historical folders as immutable, ungated sources on one archive initiative that every migrated node cites as evidence. - Resumable and idempotent: Records every successful send in .mma/.zz-migrated.json, so an interrupted run resumes where it stopped and never mints duplicates. - Use Case: A team with a repository containing a .mma/ directory runs a dry-run rehearsal, reviews the counts, then imports several hundred records into their ZZ deployment in minutes. ## Quick Start Run the zz-migrate skill from inside the mma repository to rehearse the import with a dry run, then confirm to migrate its history onto the platform.
