Back to app index

Proposal: Patch a “Global WBS” from Local Project Data using Sheaves

Toy scenario

Two complementary prototypes are proposed: (A) a strict “global section / obstruction” checker using a cellular-sheaf library (PySheaf), and (B) a diffusion/spectral layer (Neural Sheaf Diffusion + persistent sheaf Laplacians) that makes inconsistencies show up as learnable, localisable signals. The interactive canvas below is a concrete specification of what we would ship first.

0) Alignment to the Project’s Ends → Ways → Means

The claim is: a “global WBS view” is a global section; incompatibility is a non-vanishing obstruction (or a flagged residual). The two approaches differ mainly in whether you want hard certificates (A) or soft localisation and learned diagnostics (B).
Ends (global, continuous, metric-ready)
  • Global view patched from local data = compute H⁰ (global sections) and show the section explicitly.
  • Continuity = local agreement on overlaps (interfaces) implies a unique glued plan; discontinuities are “where restrictions disagree”.
  • Metric-ready = evaluate a functional on the global section (expected risk, staff-hours, schedule slack), and/or a spectral invariant on the sheaf Laplacian.
Ways (sheaf/cohomology pipeline over WBS graph)
  • Model WBS as a category (objects = work packages; arrows = dependencies/interfaces).
  • Attach local data to stalks (risk sets, resource functions, interface specs).
  • Restriction maps encode interface conditions (handover, precedence, tolerances).
  • Then: glue if possible; else compute obstruction / residual and localise.
Means (interactive HTML + LLM-friendly analytics)
The MVP is an explorable WBS graph, editable local data, and a “Glue” button that either returns a global section or highlights the minimal conflicting overlap(s). Everything else is second-order polish.

What changes in practice

Old world: "Does the plan work?" → meetings, gut feel, spreadsheet juggling.

Sheaf world: "Does a global section exist?" → a yes/no + explicit witness.
If no: "Where is the obstruction supported?" → highlight overlaps/edges + remediation hints.