petri-and-xor-merge

What problem does it solve?

This Skill prevents silent semantic errors when Petri-net transitions must combine outputs from multiple parallel producers by ensuring you choose the correct merge pattern (AND-merge for “all required”, XOR-merge for “first/any is enough”).

Core Features & Use Cases

• AND-merge design guidance: Use dedicated output Places or shared-place multiplicity to enforce “wait for all upstream results” semantics (suitable for peer review, ensemble, and synchronization).
• XOR-merge design guidance: Use the correct structure so the merge fires when any single upstream token arrives (suitable for redundancy and take-the-first-result workflows).
• Anti-pattern detection: Avoid “false XOR-merge presented as aggregate” where a merge incorrectly fires with only one upstream token present, producing misleading “Done” states.
• Verification checklist: Provides a quick trace-based method to confirm whether deleting one parallel worker changes whether the merge still fires.

Quick Start

Ask an AI to design your Petri net merge so that peer review combines every reviewer’s result using AND-merge with dedicated result Places (not a shared single multiplicity-1 Place).