pentaphase-structural-architect

Use this agent at the boundary between phases of a pentaphase structural overhaul. The agent reads the artifact produced by the just-completed phase and verifies that it satisfies that phase's gate criteria before the next phase begins. Examples — <example>Context: User just produced phase-1-landscape-report.md and is about to start phase 2. user "Phase 1 done — proceed to taxonomy?" assistant "Before we move on, I'll use the structural-integrity-auditor agent to verify phase 1's report meets the gate criteria." <commentary>Phase boundary reached — auditor must sign off before proceeding.</commentary></example> <example>Context: User completed ingestion in phase 4 and wants to verify integrity. user "Ingestion complete. Did anything break?" assistant "Let me invoke the structural-integrity-auditor to run the post-ingestion audit." <commentary>Integrity check is the auditor's core function for phase 4.</commentary></example> <example>Context: User is in phase 5 governance and wants to confirm the charter is complete enough to onboard contributors. user "Are the governance docs complete?" assistant "I'll use the structural-integrity-auditor to assess phase 5's charter against its gate criteria." <commentary>Governance charter falls under the auditor's scope.</commentary></example>

Phase 5 of the pentaphase structural-overhaul protocol. Codifies operational protocols, onboards the ecosystem of participants, programs behavior monitoring, and establishes an iteration cadence so the substrate evolves rather than calcifies. Use when the user invokes phase 5 of an overhaul, asks to "establish governance" or "lock in the protocols", or has completed ingestion and is ready to declare the substrate operational. Consumes phase-4-ingestion-report.md; produces phase-5-governance-charter.md, which closes the protocol.

Phase 1 of the pentaphase structural-overhaul protocol. Inventories assets, maps current flow, identifies friction, and defines value metrics for any substrate. Use when the user invokes phase 1 of an overhaul, requests a baseline audit, asks to "discover the landscape" of a system, or wants to understand current state before redesigning. Produces phase-1-landscape-report.md.

Threads the full five-phase structural-overhaul protocol — landscape discovery, taxonomy design, environment configuration, systemic ingestion, governance evolution — for any substrate the user names. Use when the user requests a structural overhaul, system redesign, or end-to-end restructuring of a documentation system, asset registry, code monorepo, knowledge base, or operational workflow; or when they explicitly invoke the pentaphase methodology. Coordinates handoffs between phase-skills and seats validation gates between phases.

Phase 3 of the pentaphase structural-overhaul protocol. Translates the taxonomy model into objective technical criteria, evaluates candidate mechanisms or frameworks, instantiates the chosen architecture, and programs validation rules. Use when the user invokes phase 3 of an overhaul, asks to "select a system" or "configure the environment", or has a taxonomy model and is ready to choose technology. Consumes phase-2-taxonomy-model.md; produces phase-3-environment-spec.md.

Phase 4 of the pentaphase structural-overhaul protocol. Purges redundancies, enriches and aligns legacy entities to the new schema, executes phased ingestion into the new environment, and audits integrity. Use when the user invokes phase 4 of an overhaul, asks to "migrate the data" or "ingest into the new system", or has a configured environment ready to accept legacy entities. Consumes phase-3-environment-spec.md; produces phase-4-ingestion-report.md.