Framing the question for a project review
A sheaf-inspired model treats each work package as a local view and asks whether its declared interface facts agree with neighbouring packages. Explore what that question could add to a review before design, procurement or cost commitment.
Fragmented WBS views create contradictions nobody owns
Package plans can each look sensible while the combined scope still contradicts itself at interfaces.
Relate local data through a project graph
Attach local data to packages and define what must match on the overlaps between them.
Enforce agreement where packages overlap
If Civils and Utilities share a corridor, the corridor facts must reconcile rather than merely coexist in separate files.
Locate the illustrated disagreement
The authored graph highlights selected package statements that cannot all hold under the stated interface rules.
What would a trial on project records require?
Start narrow: one station box, corridor segment, reservoir zone, or package cluster with real interface pressure.