Strategy registries and dynamic team topology in AgentPlat

Name the strategy that produced the decision

The strategy reference describes registries for allocation, team formation or negotiation, and evidence fusion. Reference implementations are deterministic and replaceable through explicit identifiers and versions.

In an illustrative allocation experiment, retain the strategy identifier with the run. Otherwise, a later configuration change can make it impossible to explain why the same apparent inputs produced a different assignment. A current default is not a historical record.

Team topology is not the peer overlay

A team topology describes the operational organization of roles and coordination. A sparse Mesh overlay describes bounded peer connectivity. Changing one does not automatically justify changing the other.

For example, splitting a research team into specialist groups is different from selecting replacement network neighbors. Keep both decisions explicit if an application changes them together, with the appropriate evidence and owner for each transition.

Preserve the old topology when installing the new one

The dynamic-topology reference includes coordinator replacement, team split, merge and federation. Each transition binds the previous digest, next epoch, evidence, authority policy and lineage. Activation is gated and rollback produces a receipt.

For a proposed merger, show the original teams and the intended successor relationship. Do not overwrite the old arrangement before the required transition is admitted. That history is necessary to interpret work that was assigned under the previous organization.

Morphogenesis composes these owners

The operator catalog uses existing topology owners for split, merge and federation. It does not turn a proposed organizational change into a direct topology update.

When evaluating an operator, trace its plan into the topology boundary and inspect the receipt returned. A model recommending a different team structure is advisory input; the gated activation remains a separate event.

Compare outcomes under recorded conditions

• Pin the strategy identifier and version.
• Record the original topology digest and intended change.
• Inspect the activation policy and evidence.
• Test rollback or rejection with its retained receipt.
• Measure the resulting work under the same declared scenario.

The reproducibility checklist helps preserve those conditions. A valid topology transition demonstrates a governed change; better mission performance still requires a separate measured result.