GIMMER / HIGHER AUTONOMY

PETRI NETS → MONOIDAL STRUCTURE → WORK PLANS

Connect the work.
Keep the freedoms.

Toy scenario

Two independently ready refuge tasks need lifting equipment. Does giving them one lift or two change only the timing—or which actions are possible together?

Compare one lift with two

The wider aim: reusable work packages that preserve lawful project options when connected. Here, the comparison isolates resource sharing. Petri nets → open boundaries → monoidal structure. Then ask whether the same contract can be stored more compactly.

THE EXECUTABLE ESSAY

Change the supply. Inspect the possible work.

Local to this browser

The pieces and their boundary

Change the starting supplies

Local tokens and unconnected input supplies belong to this scenario. A connected input’s old external supply is discharged; changing it cannot create a second token.

CURRENT FINDING

Preparing the example…
Inspect or edit the full construction

Change the fragments, event signatures, durations or named port connections. Checking validates the whole construction. An invalid edit keeps the last valid example available; it cannot silently become a result.

Keep and reopen a construction

Save one copy in this browser or download a portable JSON file. Opening a copy recomputes the result; imported findings are never trusted. No file, repository or remote model is overwritten.

No browser copy saved in this session.

EXTENDING THE SAME BOUNDARY CONTRACT

Can we store less without forgetting which work is done?

Two suppliers, A and B, each produce one support token. C consumes one. Every named task must occur once. This comparison extends the boundary contract above: store exact resource rules instead of expanded state tables. Choose an initial token, then try C first.

Why merely keeping the token count fails

After A and after B there is one token, but different work remains. If those situations are merged, the A-step available after B is also offered after A. The apparent sequence A → A repeats a once-only occurrence. Individual edges are insufficient: a continuation must work from every situation its summary represents. It already fails our promise to report named completed work.

What this attempt found: named completed-work observations prevent state merging in this model. An exact rule encoding can nevertheless avoid storing the expanded tables. Added supply changes the possible work while the receiver’s rule stays adequate. This is a bounded construction and an elementary structural argument, not a new general compression theorem.

Follow sources → rules → checks → limits · Inspect the reproducible cases

The controls affect only this demonstration; reload resets it. They do not change the main workbench or save a project record.

PURPOSE & FOUNDATIONS

From reusable work packages to lawful plans.

The aim is to compose recurring pieces of work without imposing an unnecessary order or inventing resources. Petri nets make the mechanism explicit; monoidal structure describes how its executions combine. This lab proposes a boundary contract that retains resource demands, partial states, outputs and joint steps. The papers supply the foundations; the restricted contract and its checks are our construction.

Petri nets, open boundaries and monoidal structure — the three layers
1

Petri nets: what can happen?

A circle holds tokens representing resources or conditions. A task box consumes its input tokens and produces its outputs. Borrowing and returning a lift is a pair of ordinary arcs, not an unlimited permission to use it.

Lift : L → L ⊗ R

L is an available lift; R is an installed roof. The token’s return permits later reuse. This lab separately marks selected events as once-only.

2

Open Petri nets: how do pieces meet?

Expose places through named input and output ports. Connecting compatible ports identifies their places: the two packages now refer to the same resource. Two names must not become two lifts.

Baez & Master · Open Petri Nets

The lab uses restricted wiring and an explicit supply convention; the paper treats a more general construction.

3

Monoidal structure: how do actions combine?

Markings are objects; executions are arrows. Composition (∘) joins actions through matching intermediate markings. Tensor (⊗) combines resources or actions alongside one another. An identity carries untouched resources through a step.

Baez, Genovese, Master & Shulman · Categories of Nets

We use its commutative count-token interpretation, a particular SMC. Equal arrows alone do not establish that tasks can start together.

Connecting open nets assembles a mechanism; composing arrows describes an execution within it. These are related operations at different levels. The practical question comes from Wynn & Clarkson’s ASM2.0 work: can reusable process descriptions earn their maintenance cost when context changes?

Scope: this is a finite, once-only, selected-work construction—not a complete engineering model or general WBS generator. The forward generator explores alternative work branches; the feedback trial handles review and rework. Here, timing is an added illustration, and a lawful execution need not fit one elementary WBS tree. Follow the full source → construction → limitation map.

WHY THIS MAY HELP

A reusable piece needs an explicit boundary.

The benefit is modest and testable: change a refuge method or resource arrangement, and see whether the combined work keeps its lawful alternatives. The source literature’s warning remains: context can make reusable process modules more trouble than they are worth. This example tests one piece of that problem.

Read the full construction and sources · Build and independent challenge · Source code