Mountain refuge build — treating change requests as sheafification steps
A tiny, self-contained prototype: local phase-level “helicopter flights/day” plans are patched into a single project-wide curve (a global section).
A change request modifies the cover/overlaps, then we re-sheafify and inspect the induced change in the global curve.
Controls ?
Plan: Baseline
Change request (CR-07): Add a communications mast delivery+install window that overlaps the roof and utilities phases.
The mast requires 4 helicopter flights/day on days 10–11 (heavy steel + concrete).
?
Gluing status ?
—
Peak flights/day ?
—
Total flights (sum) ?
—
Δ cost vs baseline ?
—
Interpretation in this demo: each phase submits a local “best guess” for the single global helicopter schedule on its own time window.
If two phases overlap, they must agree on that overlap for the locals to glue into one consistent global schedule. This is exactly the “agreement on overlaps → gluing”
idea used in the resource-allocation draft paper you shared.
?
Visual model ?
Cover U = {phases…}
F: “flights/day” presheaf ?
Click a phase bar to inspect its local dataClick a day tick to see overlap detailsTry: Baseline → Sheafify → Apply change → Sheafify