One platform. Many verified outcomes.

One enterprise platform supplies nine shared services, including Mission Control as the meta-factory control plane. A portfolio starts with Software Delivery and adds Modernization, Security Remediation or other factories only when their governed contracts differ. Factories compose shared Agents, Harnesses, Tools and Skills, Models and Execution Profiles. These architectural layers are dependencies, not sequential runtime steps. The separate delivery flow is Intent, Plan, Route, Execute, Verify, Release and Learn. Approval controls release; the product is a verified outcome.

Mission Control coordinates an Objective. Intent defines the desired outcome. Plan decomposes it into WorkOrders and Tasks. Route selects qualified factories and capabilities. Execute runs governed Attempts in bounded environments. Verify checks independent proof. Release promotes the exact approved Candidate. Learn uses observed outcome signals to propose evaluated improvements. The delivered product is a verified outcome; required production criteria must be observed. The seven-step enterprise summary does not replace the factory evolution lifecycle, detailed runtime states, or evidence and approval protocol.

The anti-pattern duplicates an agent stack, model integration, context, runtime, credentials, observability, policy, verification, evidence and qualification for Teams A, B and C. The preferred architecture centralizes those common services under one governed enterprise platform and reusable capability ecosystem. Factories A, B and C compose qualified capabilities for distinct outcome contracts while preserving tenant and authority boundaries. Increase builders, repositories, concurrency and workloads without creating another control plane or factory for every team.

An Objective enters Mission Control. Level one determines participating factories. The Plan decomposes into WorkOrders; level two selects and pins qualified Factory Versions and profiles. WorkOrders contain Tasks; level three selects qualified Agent, Harness, Model, Tool or Skill and Execution Profile combinations. At every level, requirements pass through policy, authorization, compatibility and qualification filtering before eligible candidates are ranked. A selected route is pinned and recorded. No eligible route means blocked or escalated, never an unqualified fallback.

Execution produces an artifact and evidence tied to exact Candidate and input identities. Independent local verification checks WorkOrder and Task contracts; global verification checks the integrated Candidate against the Objective. Both required scopes need current passing proof for the exact integrated Candidate before approval can authorize release. Missing, failed or stale evidence blocks release. Changed upstream artifacts invalidate affected downstream proof. Correct or re-execute within policy, then return to independent verification and obtain fresh approval for a changed Candidate. Release is controlled promotion, followed by required production observation.

A Factory Definition describes a governed composition around an Outcome Contract. It combines Workflow, qualified Agents, Harnesses, Tools and Skills, Models, Context, an Execution Profile, Policy, Verification and Evidence Requirements. Pin the exact configuration and qualify its interactions as a composition for a declared workload. Passing qualification produces an immutable qualified Factory Version. Activation and execution still require authorization; changes return through qualification. A component or workflow alone is not the factory.