Handle agent convergence

Results from multiple children must not combine into authority none of them possessed.

01 / The operating case

What changes in a real workflow?

A research child finds a payee, while a finance child has approval to prepare but not release payment.

Trace the authority boundary
  1. 01Authority origin
  2. 02Task and grant
  3. 03Current decision
  4. 04Observed outcome

02 / Decision contract

What the executor must check

Keep output provenance, intersect applicable task grants at the parent and require an independent payment-release right at executor.

InputPrincipal · task · action · target
DecisionGrant ancestry · policy · current state
ResultEnforce · record · verify outcome

03 / Failure and evidence

What goes wrong, and what can be proven?

Failure mode

The parent unions child capabilities and infers it may release payment.

Evidence to retain

Record contributing child outputs, grants, final decision and downstream result.

04 / Canonical scope

Why this reference stands alone

Fan-out handles splitting work; convergence handles recombining outputs without privilege union.

Illustrative implementation artifact

Convergence rule

result = combine(childA.output, childB.output)
provenance = union(outputReferences)
authority = intersect(originGrant, parentGrant, currentPolicy)
never authority = union(childA.grant, childB.grant)

Primary references

Read the underlying material

Architecture discussion

Choose one consequential action and make its boundary explicit.

Request a Conversation