Library · graph representations
What changes when a relationship becomes something you can inspect?
The things we do
Boxes are tasks. Arrows are supplied relationships.
The relationships we inspect
Read the selected relationship
(A → B) → (B → C)
Each dependency becomes a node. A new arrow means two dependencies can be followed consecutively through a shared task. Sharing only a start or only a finish does not qualify.
Try A fork, then Two separate arrows. Both produce two unconnected line nodes. Their endpoint labels tell them apart here; the line-graph shape alone cannot. Isolated tasks disappear entirely.
A → [relationship] → B
Keep tasks too inserts one distinct relationship object per original arrow. Source and target roles stay explicit. This is useful when a dependency needs its own reason, owner or evidence.
The task and relationship records are retained, including isolated tasks and parallel arrows. This app can reconstruct the original records from this view; shared relationship objects would change that guarantee.
A representation choice. The shelter's arrows mean finish-to-start prerequisites: roofing and the door must be finished before painting. A route through the line graph is not an alternative way to satisfy that join. The drawings do not calculate dates or resources, discover missing tasks, or establish the supplied dependencies.
This is a dependency network, not a WBS hierarchy. Nor is it an activity-on-arrow schedule: its new boxes represent dependencies, not events, and it does not turn the tasks into arrows.
To explore how actual graph edits change a plan, use the Graph-change workbench.
| ID | Task |
|---|
| ID | From | To | Label |
|---|
Use a small directed graph: up to 24 nodes and 48 edges, each with its own ID. Duplicate labels, parallel arrows and loops are allowed. Additional JSON fields stay with the original records.
Work stays in this tab. Download the source to keep it; load that file to return. “Current representation” exports the computed graph for inspection. Incidence exports can also be loaded here; a line export is a derived view, not a replacement for your source.
The directed line-graph rule follows NetworkX's definition and loop convention. The incidence view keeps the node–edge distinction and source/target roles explicit; compare the oriented incidence-matrix definition. Here separate links retain both roles even for a self-loop.
The original “WBS Graph Transformation Demo” supplied the six-task shelter network and paired graph views. This browser version retains those, corrects the direction and loop rules, and adds stable relationship IDs, selectable traces, contrasting examples and a representation that keeps the original objects. The extra views and project interpretation are this example's construction.