Every entity is a node, every real-world dependency is an explicit edge, every change is an event whose consequences propagate through the graph. The project stops being a static plan you reconcile monthly — and becomes a system that foresees its own future.
Why megaprojects need a different object
A megaproject is not a big project; it's a small economy. Tens of thousands of activities, hundreds of contracts, shared labor pools, regulatory clocks, and commodity exposure — all coupled. The tools of record store this as flat lists and static baselines, which is why consequence-finding is a manual craft: something slips, and an army of planners spends weeks discovering what it touches.
Prognode stores the project as what it actually is: a network. Entities — activities, contracts, permits, crews, deliverables — are nodes. Real-world dependencies are explicit, typed edges. Changes are events. When an event lands, its consequences propagate along the edges automatically: what's delayed, what's starved, what's now critical, what it costs.
Flat list
| ID | Activity | Date | Status |
|---|---|---|---|
| A100 | Backfill | May 21 | Planned |
| A150 | Steel Erection | May 21 | Planned |
| A130 | Found. pour | May 21 | Delayed |
| A170 | Drywall | May 21 | Planned |
Living graph
Same slip. One of these knows what happens next.
Foresight and memory
The graph doesn't just record the project — it tests changes before they happen, and gets sharper every time one actually does.
Test the change before it happens
Run what-if events against the live graph — a supplier slips, a permit stalls, a scope adds — and see the propagated consequences before you accept them into reality.
The project learns from its own history
Every event and outcome is retained. The graph's forecasts are conditioned on what this project has actually done, not just what the baseline hoped — so the model gets sharper as the project ages.
Built to avoid ruin
Underneath the graph runs the same discipline as everything we build: survival first. Prognode's engine is architected to keep the project off the paths that end in non-recoverable loss — the compounding delay chains, the resource collisions, the commitments that only work if everything goes right. It flags them while they're still cheap to avoid, and it prices what it would take to get off them.
Prognode + Chronova
Prognode answers the question inside one enormous project: given everything that just changed, what happens next and what does it cost? It is the instrument you point at the asset that is big enough to have its own weather.
Chronova answers the question across the book: given every claim on the capital, how much should each one get? Run together, the graph's live read on a mega-project feeds the sizing decision for the portfolio that contains it — one project's slip becomes the whole book's reallocation.
Bring us your hardest project
If it's big enough to have its own weather, it's big enough for Prognode.
Start the conversation