Morphogenesis operators and compensation journals

Choose the exact operator family

The operator reference distinguishes role realignment, work reassignment, replacement, suspension, resumption and topology transformations. Each family is enabled separately with its own limits.

An illustrative request to replace an unavailable specialist is not equivalent to creating a new lineage or splitting its team. Select the operator whose owning boundaries match the intended change rather than treating every adaptation as a generic update.

Follow the plan before the effect occurs

The documented execution model persists the compiled plan and state before crossing an external boundary. Stable operation IDs make attempts reconcilable after interruption.

Inspect the plan's steps and owners before activating the change. If a worker stops after one owner commits, the next process needs to know which operation it is reconciling. Rebuilding an unrelated plan from the current prompt can lose that relationship.

Keep compensation separate from the original execution

Pre-commit compensation uses its own journal and runs in reverse applied-step order. That records the attempted response to a partial execution rather than rewriting history as if nothing happened.

For an illustrative temporary specialist, cleanup may involve detaching or retiring the agent and releasing its budget through the documented lifecycle. A useful review follows both the original boundary receipt and the corresponding cleanup outcome.

An unknown outcome must remain unknown until reconciled

The operator guide explicitly stops progress on an indeterminate effect. A missing acknowledgement is not proof that the owner failed to apply the transition.

The operations guidance calls for exercising crashes around external boundaries and collecting receipts. Use those scenarios to verify the journal's explanation, including states that require reconciliation instead of an automatic next step.

Preserve authority ownership throughout cleanup

The governance model keeps work, membership, roles and actions with their owners. Compensation does not create a new unrestricted authority path simply because it is responding to an error.

1. Inspect the selected operator and enabled limits.
2. Identify each persisted step and boundary owner.
3. Inject a bounded failure after a chosen commit.
4. Follow reconciliation and compensation receipts.
5. Confirm the remaining organizational state is explicit.

Report partial cleanup honestly. A journal is useful because it exposes what happened, including what could not be reversed.