Ends · What we want
Make project dependencies, hand-offs and readiness conditions visible enough to question, explain and reuse.
The original catalogue identifiers are retained.
Toy scenario
Brickwork needs materials, labour and access. Roof work needs a wall with the right readiness and support. The examples make these package interfaces explicit so that connecting two diagrams also means connecting compatible conditions and promises.
When do individually acceptable work packages make an acceptable whole?
Enquiry · Composing work packages
Method · Project wiring diagrams
What must one piece of work provide before another can begin? Make those interfaces explicit, then explore how small project blocks can fit together and be reused.
The wider enquiry
The construction example is a starting point. The larger question is whether a project can be assembled from understandable blocks, each with a clear boundary and an account of how it behaves.
Make project dependencies, hand-offs and readiness conditions visible enough to question, explain and reuse.
Connect typed inputs and outputs, attach explicit conditions, and compare a module with the work it contains.
Small interactive models, wiring diagrams, port tables and computed checks, supported by the language of composition.
How this started. The Substack sequence begins with boxes and wires for project scope and develops into a string diagram for a building. Those posts preserve the early question; the essays here make the interfaces, readiness conditions and corrections explicit.
These are exploratory teaching models. Their checks concern the rules represented in each model; they do not establish engineering safety, a complete schedule or suitability for a real project. Selected older operad, contract and serial-wiring experiments have received scope corrections; other earlier experiments retain their original exploratory status.
Start here · Interactive essay
Follow a small construction example from materials and preparation to a wall and roof. Inspect what each process needs and produces, change its readiness conditions, and see what those choices mean downstream.
Open the essaySeparate a correctly connected diagram from work whose stated preconditions are satisfied.
Explore a module through its inputs and outputs, and open it to inspect the work inside.
Read computed checks against the model’s explicit rules and see the limits of what they establish.
Six essais · one enquiry
Open a wall module. Follow both workers, the materials and returned access. A replacement must keep more than the shape of its ports.
See what an operad algebra actually supplies. Compute relations, inspect typed composition laws and eliminate hidden wall–roof variables.
Carry materials and a growing wall through repeated work. Discover why emitting two courses is not yet building one wall.
Move a revision across an explicit information-copy box. The port types stay the same while the wall and roof records cease to agree.
Interleave schedule, resource and approval updates. Distinguish a harmless coordination gap from a missed recovery deadline or work during disagreement.
Keep package internals fixed while varying standard interfaces, shared crews and common failure exposure. Test containment against setup cost and all-or-none acceptance.
Earlier explorations
The catalogue keeps all thirteen experiments reachable. Six maintained essais now connect the resource model, its algebra, repeated work, revisioned information, coherent histories and failure containment. The seven earlier experiments retain their distinct workings; their limits are described at the relevant entrances.