Lifecycle and operators (V1–V2)
V1 catalog lifecycle
V1 uses a fixed, digest-bound Workflow definition:
observe → assess → propose → decision_gate → verify_decision → prepare
→ provision → attest → enroll → activate → await_outcome
→ drain → evaluateThe first vertical slice either recruits an eligible existing agent from a declared bounded view or creates a catalog-certified temporary specialist. It activates a successor Team, preserves causal work, commits one morphology head, checkpoints and fences authority, then detaches or retires the temporary agent and releases its budget.
Candidate absence means only “none found in this declared bounded view.” It is never a global claim that no suitable agent exists.
V2 profiles
AgentInstantiationProfileV2 supports catalog, derived and synthesized
modes. Derived and synthesized profiles bind parent profiles and lineage,
material evolution, capability evidence and attenuated tool, action, resource
and interaction ceilings. Synthesis requires an independent certification.
A profile is not an identity, role, membership record, capability proof or authority grant. It is input to the existing governed factory path.
V2 advanced operators
| Operator | Existing owner used by Morphogenesis |
|---|---|
derive_agent | Governed factory, lifecycle, Trust and Team Formation |
realign_role | Inference Control role realignment |
reassign_work | Mission Lifecycle and successor Work receipt |
replace_agent | Lifecycle, Team, continuity, fencing and retirement |
suspend_agent | Continuity, Work/Action fence and Membership exclusion |
resume_agent | Checkpoint, active key, Membership and Work rebinding |
split_team | Certified Dynamic Topology transformation |
merge_teams | Certified Dynamic Topology transformation |
federate_teams | Certified federation that preserves source Teams |
Each operator family is enabled separately and has independent population, depth, role, Work, replacement, suspension and topology limits.
Durable execution and compensation
The compiled plan and execution state are persisted before an external boundary is crossed. Stable operation IDs make retries reconcilable. Pre-commit compensation is a separate journal and runs in reverse applied-step order. An indeterminate effect stops progress; it is never guessed to have failed or succeeded.