Project Risk Topology

Find Critical Paths Your Gantt Chart Misses

Standard project tools model declared dependencies — what is written in the schedule. IRDME finds hub shadows: subsystems that are invisible in the dependency chain but are hubs in risk and resource coupling. These are the failures your Gantt chart cannot see.

Hidden Critical Paths

Low Gantt rank, high risk coupling rank. Failure cascades mission-wide — the schedule never warned you.

Budget Bottlenecks

Hub in the resource-sharing layer but not on the declared critical path. Every budget cut hits more systems than the plan shows.

Mission-Critical Systems

Universal hub — top-ranked across all three layers. Declared, structural, and risk coupling all agree.

Project Configuration

Demo: Mars Mission Architecture (12 subsystems · 3 layers). Replace with your own project JSON.

Requires a free IRDME account. Create one →

How Project Risk Topology works

  1. 1. Model three layersdependency_chain (Gantt) · resource_sharing (budget + personnel) · risk_co_occurrence (failure cascades)
  2. 2. Compute cross-layer hub persistenceIRDME runs Pearson + Spearman correlation of hub importance scores across all layer pairs.
  3. 3. Detect hub shadowsA subsystem is a hub shadow if it ranks high in risk coupling but low in the declared schedule — invisible to standard PM tools.
  4. 4. Classify each subsystemMission-Critical (universal hub) · Budget Bottleneck (chameleon) · Hidden Critical Path (Gantt blind spot) · Peripheral
Based on the Functional Proximity Law (IRDME, arXiv:2604.23639) — 16 confirmed domains including software, biology, finance, and infrastructure.Read the paper →