Unpack Union

Splits a union-typed stream into one output per variant. Exactly one output ticks per input message — the variant that matched.

How it fits

{{type:t1|t2}} -> {{component:unpack_union}} -+-> {{type:t1}}
                                              +-> {{type:t2}}

Typical backends

• Type-routed event handling: heterogeneous event source built via {{component:pack_union}} -> {{component:unpack_union}} -> per-variant downstream stages.
• Error vs payload routing: {{component:pack_union}} -> {{component:unpack_union}} -> {{component:filter}} per branch.
• Multi-modal demux: pack_union from text + image sources -> {{component:unpack_union}} -> separate processing chains.
• Command dispatch: union of command shapes -> {{component:unpack_union}} -> per-command-kind workers.

Caveats

• Each input tick fires exactly one output branch; the others stay quiet that tick.
• Downstream stages on inactive branches must tolerate gaps in cadence.
• Variants must be jointly exhaustive — every value falls into one declared branch.