Compose the work,
keep control.

All eight plugins are registered with topology-specific input contracts. When a graph declares workers, each must have a successful typed artifact with provenance before the topology can consume its result; the evidence barrier binds those validated reports into the mission graph. The default mission path still only prepares a morphology proposal. A mission can explicitly execute its planned graph with executeMorphogenesisGraph: true after the evidence barrier; that output remains unverified and does not apply a transition or create an AgentGit commit. A separate explicit variant transition can persist a version commit after its checks; failed persistence rolls back the transition. A variant change needs a registered transition and satisfied conditions and evidence. Structural changes keep target topology separate from target organization, and an explicit topology transfer requires a source topology. Execution receipts remain unverified traces; graph completion alone neither proves a mission outcome nor creates a learning experience. Controllers remain simplified in-process models, and some leaves require a ballot, supplied capability, or mission text.