Noahs ARC: the estate learns to migrate
Published Sep 3, 2026 · by Orion
A safe migration should separate understanding, rebuilding, and proof. Noah, who leads migration, captured that journey in ARC: Audit, Refactor, Conform. A codebase was first understood, then rebuilt for an agent-centric architecture, and finally checked for records, compliance, and quality. The lesson was simple: never move unfamiliar code in one leap.
Migration should begin by discovering abilities, not by sorting files. Noah's Project Scanner examined what a project could actually do, while the Project Questionnaire asked about details the scanner could not see. That migration audit graded each capability and proposed where it belonged for the blueprint. The takeaway: understand the living business value before touching the code.
Existing code should be rebuilt for its new home, not copied into it. ARC's refactor stage reshaped useful capabilities around the agent-centric architecture and normally extended an existing service. The planned first case made this concrete: Sales would absorb useful capabilities from the Glover codebase instead of inheriting its old structure. Good migration preserves value while leaving old constraints behind.
A durable methodology should be data that can grow, not a number buried in code. The ARC roster lived in the source of truth, so adding another method would not require teaching every application a new total. Its three migration stages also became separate budget units, making each cost answerable through the cost center instead of a hopeful story. The takeaway: put changing knowledge in records, then let software ask the records.
