GratisAI career · find the delivery floor hidden in a project’s dependencies · local-first FREE TIER 1 Free Run Available
dependency-rung route · climbing rung ladder

Find the Delivery Floor Hidden in a Project’s Dependencies

A list of task lengths hides the work that must wait for other work. Enter durations and predecessor names to expose earliest starts, earliest finishes and the longest dependency chain before promising a delivery day.

1 · task | duration workdays | predecessor labels, or -

FIRST-LOAD

HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.

Data note: The dependency-rung route processes task | duration workdays | predecessor labels, or - locally. Starter/sample selection and Run compute in this tab; no input is sent by the calculator. A local draft may be saved; explicit state-link sharing or optional external AI formatting can disclose inputs. Use non-sensitive labels.

Perspective: Before: task lengths hid which handoff controlled the finish. After: the longest dependent route and each task’s float are visible, while resource constraints remain a separate question.

2 · Read the dependency-rung route

Dependency arithmetic only, not a delivery guarantee, staffing recommendation or employment assessment. It assumes unlimited parallel resources and omits calendars, uncertainty and fixed constraints. Confirm the route and available people with the project owner before making a commitment; do not use it to judge workers.

Optional filing controls are a local prototype.

Checkout is unavailable. The reading above is complete; print, CSV and five local summaries are optional enhancements, not hidden answers.

Before using the dependency-rung route

Start with a small deliverable whose handoffs you understand: a portfolio prototype, internal process update or team training artifact. Give tasks stable short labels, then ask each owner what must be finished before their task can begin. A dependency is not merely a preference for doing one thing first. If a review truly needs the prototype, connect it; if research and layout can proceed independently, do not manufacture a link between them. Duration means elapsed working time in this model, not a count of person-hours. The output is a lower bound under unconstrained parallel resources, not a project promise. Keeping that distinction visible makes the result useful in a planning conversation without turning an arithmetic route into a staffing forecast.

Boundary and sources

Dependency arithmetic only, not a delivery guarantee, staffing recommendation or employment assessment. It assumes unlimited parallel resources and omits calendars, uncertainty and fixed constraints. Confirm the route and available people with the project owner before making a commitment; do not use it to judge workers.

Mechanism: competence-autonomy-loop

Optional AI formatting, never the calculation

Manual entry completes this dependency-rung route for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.

Format only these fictional or non-sensitive notes for a dependency-rung route. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string"]}], "setting": "string"}. The columns are task | duration workdays | predecessor labels, or -; the setting is Planned delivery window in workdays from day zero. Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.

An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.