Operations, security and evidence

Durable state

Production-oriented compositions persist Workflow state, morphology heads, execution journals, outcomes, strategy governance and required subsystem receipts. PostgreSQL stores use revision/digest compare-and-set, logical-time high-water marks and external rollback witnesses. Temporal may provide wakeups, retries and history rollover; it does not own authority.

Primary threats

• stale, rolled-back or equivocating source heads;
• proposal replay across scope, epoch, policy or budget;
• self-approval and dependent reviewer collusion;
• effect repetition after a crash or lost acknowledgement;
• forged Membership, Trust, role, Work or Action evidence;
• remote Mesh evidence treated as local authority;
• unsafe learned or synthesized strategies;
• descendant creation that widens an authority ceiling;
• partial multi-owner evolution presented as atomic success;
• constitutional fork or rollback.

Controls include strict schemas, exact digests, bounded views, TTLs, CAS, stable operation IDs, independent groups, separate authorization and fencing, content-free exchange, compensation journals and external rollback witnesses.

Operational sequence

1. Pin coordinated package versions.
2. Configure policy, decision principals and independence rules.
3. Bind durable stores and external witnesses.
4. Verify backup/restore, tenant isolation and key rotation.
5. Exercise crashes before and after each external boundary.
6. Run canaries with bounded budgets and explicit rollback.
7. Collect receipts and verify their predecessor and digest chains.
8. Promote only on deployment-specific evidence.

Evidence boundary

Source tests demonstrate implementation behavior. Simulation demonstrates only the registered scenario. Staging evidence applies only to the exact commit, configuration, topology, keys, adapters and environment measured. None of these automatically establishes production readiness or organizational improvement.

Canonical operational material lives in the open-source repository under docs/runbooks/agent-morphogenesis-beta1/ and docs/runbooks/agent-morphogenesis-beta1-staging/.