The architecture of the mesh

The mesh uses three layers.

Control plane

The Transformation Orchestrator maintains the lifecycle view: phase, workstream, dependencies, decisions, evidence and human approvals. It coordinates work but does not certify its own outputs.

Domain agents

Domain agents perform specialist transformation work across business value, process, architecture, solution design, integration, extensibility, data, security, testing, adoption, cutover and operations.

Their skills and authority differ. The Process / Fit-to-Standard Agent may create proposed backlog items. The Data Migration & Quality Agent may execute approved migration activity in a non-production environment. Neither should silently approve a material design exception.

Assurance agents

Assurance agents independently assess evidence, consistency, segregation of duties, quality-gate readiness and program risk.

This separation is intentional. If the same agent creates, reviews and approves an output, the mesh reproduces a weak human control model at machine speed.

Shared foundations

All three layers depend on:

• a connected transformation knowledge model;
• stable identifiers for project objects;
• authoritative systems of record;
• agent identity and access control;
• policy and approval services;
• observability and audit records; and
• named human owners.

The architecture is therefore both technical and organizational.