📖What it is

Audit → Refactor → Conform

The Carolverse migration methodology: how an existing codebase becomes conformant estate capability.

ARC is the methodology by which the Migration service takes a codebase that already exists — built anywhere, in any shape — and delivers its capabilities into the Carolverse: implemented agent-centric and modular, within Carolverse policies, using registered skills, frameworks and patterns. It is three segments. Audit discovers, grades and places what the source holds; Refactor rebuilds it generalised to the estate's architecture; Conform proves it belongs, completes the records, and hands it over. By default a migration extends an existing service with new capabilities rather than minting a new one. The name is deliberate: ARC is Noah's arc — the journey a codebase makes from its old shore into the estate.

📖Audit

From a reachable source to a graded capability map and an approved placement proposal.

Bind the request to its project, inventory the source, extract capabilities and requirements with evidence, grade every finding against a named Carolverse standard, and propose where each capability lands — extension into an existing service by default.

Starts when:
- A migration request exists, arrived through Noah's own door (his chat or a filed request), and names — or is resolved to — its requesting project and a reachable source.

Finishes when:
- Inventory, requirements, graded findings and a complete placement proposal exist as records, and the requester has approved the proposal.

📖Refactor

A generalised rebuild to the estate's architecture — never lifted code.

Rebuild each approved capability in its destination: agent-centric, modular, config-only customization per the instantiation ruling, within policies, using registered skills, frameworks and patterns. The registry rows, handbooks and tasks are carried as the build lands, not after.

Starts when:
- An approved placement proposal exists and the Refactor task on the migration track is funded.

Finishes when:
- Every approved capability is implemented in its destination with its records carried, and nothing crossed the boundary as lifted code.

📖Conform

Prove it belongs: compliance, tests, records, and the handover that ends the migration.

Prove the rebuilt capabilities conform — architecture compliance, policy compliance, registered passing tests — complete every record including per-stage cost, then hand over to the absorbing service's owner. Absorbs the former handover stage whole.

Starts when:
- Refactor is complete against the approved proposal.

Finishes when:
- Conformance proven, records complete, handover accepted, stage costs closed. The migration is finished and the destination service operates the capability.