The short answer

Agent Morphogenesis governs changes to a collective’s operational form, such as agents, roles, teams or strategies. A proposed change, its approval, permission to execute and the resulting subsystem receipt are distinct records. Existing subsystem owners retain their authority.

Operational form can change without unrestricted self-modification

A collective may need a specialist, a different team arrangement or a revised strategy as conditions change. The design challenge is retaining a record of why the change was needed and which owner was allowed to apply it.

The Morphogenesis overview introduces this governed evolution capability. A model suggestion or simulation result is input to that process, not direct permission to alter the organization.

Follow four records through the change

The governance reference distinguishes a proposal, a decision binding, execution authorization and a boundary receipt. Each answers a different question: what was proposed, what was approved, what may begin and what the owning subsystem actually did.

For an illustrative specialist request, keep those records separate in the operator view. Approval of a candidate does not prove that enrollment succeeded. A successful enrollment receipt does not permit unrelated external actions.

Decision routes are selected by policy

A decision can involve local policy, an authorized agent, an authorized person, a collective or a required composition of principals. A person is not intrinsically required for every decision.

That flexibility makes scope and independence checks important in the application's governance design. Decide who may evaluate a proposed change and whether the proposer can participate in that decision. Confidence in an agent's answer should not substitute for a current explicit decision mandate.

Subsystem owners still apply the effects

The governance documentation assigns creation, membership, roles, teams, work, actions and process execution to their existing owners. Morphogenesis coordinates the change and its evidence without becoming a universal authority above those components.

Trace an organizational proposal into each affected subsystem before enabling it. Identify the required authorization and receipt at every boundary. A partially completed change needs an explicit operational interpretation rather than a single optimistic “adapted” status.

Evaluate the change and its evidence separately

The operations and security guide supplies the evidence boundary for this opt-in surface. Verify the exact version and supported profile before using an advanced operator.

  • Record the observation and target change.
  • Inspect the selected decision route and scope.
  • Verify separate execution authorization.
  • Collect the relevant subsystem receipts.
  • Measure the outcome under the actual operating conditions.

A successful governed transition demonstrates that the configured process applied a change. It does not by itself demonstrate that the new organization performs better. Keep software conformance and observed organizational outcomes as separate evaluation questions.

Sources and further reading

Documentation reviewed . Consult the linked documentation for current implementation details.