The Petri net below is the declared process logic of a cliffside mountain refuge build (halfway up a cliff): tokens are “facts” (markings), transitions are “acts” (tasks). Under the “interchangeable markings/tokens” assumption, the clean categorical fit is the free commutative (hence symmetric) monoidal category presented by the net; “schedule options” are morphisms (reachability), while a WBS is a chosen operadic/parenthesized factorization of that morphism and a time schedule is a copresheaf / max-plus enrichment on the same causal skeleton. This early prototype constructs task and precedence-layer views; it does not check the proposed categorical interpretations or establish that real crews and resources can work simultaneously.
In planning, one often wants not just “the list of actions” but the trace of state (which literals/facts carry causal responsibility for later steps). A Petri marking is exactly that kind of trace-friendly state, and a schedule can be seen as a path in the reachability graph: a sequence of markings connected by firings. Treating markings as interchangeable “for now” corresponds to working in the collective-token setting where only multiplicities matter (no token identities).
A Petri net freely generates a (very strict) symmetric/commutative monoidal category: objects are markings; morphisms are firing sequences; tensor combines independent processes in the model; composition is “doing in series”. Actual simultaneous work also depends on resources and access not established by the tensor notation. This turns “project space” into a genuine algebra: schedule options are morphisms, WBS options are factorizations of morphisms, and “milestones” are just intermediate objects you choose to cut on.