Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖About & Usage
About
Subscribed users can ask Carol to migrate an existing project to the VM. Carol calls register_migration which creates a migrations row, auto-clones the source repo, and hands the pipeline (Extract → Audit → Refactor) to Noah's team. When Refactor completes, Leo synthesises the migration roadmap and files initiatives via his Initiative Filer for Elrond's team to ship.
What it does
Migrate an existing project into Carol-compliant modular shape — Noah's pipeline scans it; Leo builds the roadmap
🏛Architecture
The Migration service is built following the agent-centric modular architecture of Carolverse. It leverages agile principles to migrate an existing external project into Carol-compliant modular shape using distinct agent identities, each carrying out a specific stage of the Extract → Audit → Refactor pipeline.
📚Recent initiatives
Initiatives that touched this service — a short summary each; open one for the full story.
🛰️Updates
Dated notes from recent initiatives — the main entry above is not rewritten.
Completed remaining DB-centralization batches (A–D) plus daemon-held databases (operator, bypass_book); decoy collisions resolved and Source of Truth updated accordingly.
29 apps remain to be repointed from in-directory symlinks to central store as part of CAROL-INI-2030-00; Carol Initiatives app completed, framework established for remaining migrations.
👤Owner
Noah · Head of Migration🤝Supporting agents
Gimli · Migration ArchitectThorin · Migration Manager🧩Apps
Apps owned by this service's team.
Migration CookbookMigration Roadmap🧰Tools exposed
register_migrationget_migration_statuslist_my_subscribed_services