Act on it together

Temporal Dependency Scheduling

Find the feasible plan. Know your critical path.

Temporal dependency scheduling takes your work-breakdown — tasks, predecessors, resources, estimates — and computes a feasible plan: when each task can start, what's on the critical path, where you have slack, and what shifts when something slips. Gives a multi-person project its shared temporal truth, not just a to-do list.

Shape

Operational dimensions

Requires approval

Each output waits on a human decision.

On demand

Fires when a user asks.

Medium data gravity

Holds working state that compounds over runs.

Two-way integration

Reads from and writes to external systems.

Inputs

task list with effort estimates
predecessor/successor dependency links
resource pool with calendars and availability
actuals and progress updates

Outputs

feasible schedule (start/end per task)
critical path identification
resource allocation assignments
milestone date forecasts and per-task slack

Mechanism

Computes a feasible schedule across many work-items by resolving temporal dependencies, resource constraints, and milestones — produces start/end times, critical path, and resource allocations.

Why this is a primitive

Cannot be decomposed: the dependency-and-constraint solver (predecessor links, resource levelling, critical-path computation, schedule rebalancing under change) is a single mathematical operation over a work-breakdown. It is not per-item state progression (stateful-lifecycle), not routing decisions (workflow-routing), and not cadence execution (coordinated-sequencing) — it is the temporal feasibility computation itself.

Where it shows up

Construction project scheduling — PM enters tasks, sub-contractor availability, and dependency links; system computes feasible Gantt, flags critical path, and rebalances when a concrete pour slips

Software release planning — engineering lead inputs sprint tasks with inter-team dependencies and engineer calendars; system produces feasible release schedule and highlights blocking dependencies

Clinical trial protocol planning — trial coordinator resolves patient visit dependencies, lab processing windows, and investigator availability into a compliant per-site schedule

Event production planning — production manager plans venue setup, catering, AV, and talent arrival with dependency links; system surfaces the critical path and resource conflicts

Related primitives

Composes with

Stateful Object Lifecycle →Workflow Routing & Gating →Multi-Role Live Operational Surface →

Alternative to

Stateful Object Lifecycle →Workflow Routing & Gating →Coordinated Multi-Party Sequencing →