Critical Path & Float Risk — FAQ

Where did Path Risk / Longest Path Logic go?

They merged into Critical Path & Float Risk (ADR 0289). Old tab ids (pathRisk, drivingPaths) alias to the new workspace for deep links, commands, and telemetry.

Why is the tab empty?

Ensure a file is uploaded, prepared, and injected. Some analyses need both baseline and updates.

Analysis stuck on pending?

Check Worker Timeouts. Large files use size-scaled timeouts. The unified surface uses a persistent criticalPath.worker (load / analyze / diff / dispose).

Observed vs computed float paths?

When XER float_path / float_path_order are populated, the observed partition is authoritative. The UI reports Jaccard agreement % (membership overlap by task_code) against the computed Multiple Float Paths partition. When nothing is comparable, agreement is blank (em-dash), not 100 %.

Why did Path 1 stop mid-chain?

Path 1 follows driving edges only. If an activity has no driving predecessor, the trace breaks and a path-break defect is raised (ADR 0307). That is intentional forensic signalling, not a silent hop onto a non-driving link.

How is the near-critical threshold chosen?

Default T = 5% of remaining project duration. Override with the linked days / % controls; stored value is override hours.

Why does driving differ from “lowest total float”?

Driving uses relationship free float (RFF) ≤ 1 work-minute, not a total-float heuristic. See Float-path partition.