← Morphogenesis · all cases
01 · USE CASE · MORPHOGENESIS

Independent change
review

Review a patch through two distinct paths, then begin integration only after an explicit check.

PARALLELGATESEQUENCE
CONTEXT

When this graph
is useful.

A team wants to evaluate a code change without mistaking a persuasive analysis for sufficient evidence. Two parallel branches produce separate reports; an explicit condition then determines what happens next.

WHY THIS SHAPE

What the structure
makes explicit.

  • Parallel branches finish before the next step and each keeps its own execution receipt; receipts are traces, not proof.
  • The gate has three explicit children: a conditional topology, followed by the then and else branches.
  • The condition inspects the previous output; only the selected branch runs.
CONTRACT AND LIMITS

This composition follows the pattern covered by the SEQUENCE(PARALLEL, GATE, A-Team) test, with Rhizome as the condition and A-Team/Trinity as branches. A receipt records graph activity; supply evidence separately for the gate. Configure the condition and its expression for the mission; topology controllers remain simplified.

Compare related topologies →