Skip to content

Petri Nets — Project Candidates Across the Codebase

Petri Nets — Which Projects Could Benefit?

Section titled “Petri Nets — Which Projects Could Benefit?”

Survey of all projects under ~/internal/ and ~/external/ (48 repos total) for existing Petri net usage and candidates where Petri net modeling would add value.

None. Zero projects currently use Petri nets.

Rank Project Path Why It Fits
1 ralph-alesi ~/internal/ralph-alesi ADL phase orchestrator (Intake → Plan → Patch → Review → Integrate) with sub-agent forking, approval gates, recovery semantics. Textbook Petri net: discrete phases, guard conditions, concurrent execution, resource management (budget, history tokens).
2 opencode ~/external/opencode Concurrent session execution with tool settlement pipeline, interruption fencing, and provider-turn safe boundaries. Sessions are independent nets sharing a SQLite resource. The tool-call projection/settlement cycle is a subnet.
3 void-runner-overdrive ~/internal/void-runner-overdrive Game engine FSM with three states (Exploring, Combat, Event) and guarded transitions. playerEnergy is a natural token resource consumed/produced by transitions. Good entry-level demonstration.
4 game-of-codes ~/internal/game-of-codes Event ingestion pipeline: Verify → Parse → Deduplicate → Store (linear Petri net with inhibitor arc for dedup). XP processing subnet: event → calculate → streak → level → update. Producer-consumer queue pattern.
Rank Project Path Why It Fits
5 vaultwarden ~/external/vaultwarden Multi-step auth flows (OIDC: authorize → callback → token → redeem; WebAuthn: challenge → store → finish). Each flow is a state machine subnet. WebSocket hub uses bounded channels (buffer 100).
6 little-coder ~/external/little-coder Concurrent subagent fork/join with bounded worker pool. Event-driven extension hooks (pi.on) form a reaction network. Good for demonstrating parallel execution semantics.
Project Path Why Low
spec-kit ~/external/spec-kit Workflow catalog and step tracking — scaffolding tool, not runtime process engine
Qwen-AgentWorld ~/external/Qwen-AgentWorld Linear evaluation pipeline (inference → scoring → aggregation) — no branching or concurrency
amicron-platform ~/internal/amicron-platform TOTP calculation and CI pipeline config — boilerplate, not application logic
  1. ralph-alesi orchestrator — Most complex concurrent state machine; best demonstration of Petri net value for AI agent orchestration
  2. opencode session execution — Concurrent session coordination with resource sharing; excellent for demonstrating inhibitor arcs and shared-place patterns
  3. void-runner-overdrive engine — Simple but clear FSM with guard conditions and resource tokens; ideal teaching example
  4. game-of-codes event pipeline — Producer-consumer with idempotency; good for demonstrating workflow modeling and inhibitor arcs