Join at a boundary
Two local diagrams name the same handover. Identify that interface and see the composed graph.
From the open-graphs drawing.
Explore joining →Shared waters
Composing open systems
Toy scenario
The same people and tools can have different service capabilities when their relations change. Try a compatible handover, then separate what the arrangement can do from what has permission to happen now.
Try the same parts in a different arrangement →Four different questions
Try a shared observation, a joined boundary, an organisational comparison or a two-step service rehearsal. Each uses a different construction; none derives a complete delivery plan.
Two local diagrams name the same handover. Identify that interface and see the composed graph.
From the open-graphs drawing.
Explore joining →Make the current and intended arrangement visible. Separate what stays, what changes and what is added.
From the BAU / TOM drawing.
Explore the comparison →Leave all versions at A, then let installation request the team too. Agreement survives; the capacity rule fails.
From the open-process drawing.
Explore the interfaces →Join local transitions. Keep capability, current blockers, permission and the completed service event distinct.
A new dynamics essai · 23 October 2026.
Run the handover rehearsal →The first three trials each reconstruct one of Lawrence’s 2022 GraphML attempts, retaining what holds up or can be corrected directly. The original drawings and the reasoning behind each correction remain linked from the individual trials.
The wider question is what open-system composition helps us define: work, capability, scope, resources or services. Deriving useful project work remains an ambition, not a result of these three constructions.
Sources, corrected meanings and unresolved claims →No attempt needs to solve the whole project. A clear distinction can be a useful result.
Read the End, methods and sources →