What is actually stopping this job from closing?
NEXUS Closure Graph analyzes task dependencies, proof requirements, mandatory gates, and recovery scenarios. It produces explainable action priorities without model inference calls. Custom analysis requires a signed-in workspace.
Preview: the synthetic example is public. Custom analysis sends your JSON to the JobClosure server; sign-in and active organization membership are required. Do not enter confidential information during preview. Scenarios are planning models, not guaranteed completion dates, engineering certifications, or automatic changes to customer records.
Closure graph input
Edit this JSON after signing in to your workspace, or use the public synthetic example. Each task has a unique ID, dependencies, proof status, duration, impact, and an optional mandatory closeout gate.
Allowed statuses: todo, doing, blocked, done. Proof: none, pending, rejected, accepted, not_required. Maximum 150 tasks.
What-if recovery simulation
Shorten a remaining task and calculate whether it changes the longest dependency path. Simulations cannot bypass required proof acceptance.