Choose the project
Start from a release or a task with an explicit owner. In the demonstration, Atlas migration connects implementation, validation and the cutover decision in a single view.
Project Graph
Every dependency. One connected picture.
Connect tasks, decisions, pull requests and documents. Give your team a shared view of the work behind a delivery date.
ACDFMC+1
Illustrative workspace · interactive demonstration
Trace the whole dependency
Follow blockers across projects instead of hunting through tabs.
ENG-284Linked context
Keep the source in view
Open the originating task or decision from its linked context.
Review the range
Understand what changed
See which upstream changes affect the plan you are discussing.
Ready for reviewHuman approval
A practical workflow
Follow a change all the way to the release.
A blocked task rarely tells the whole story. Start with the relationship, trace its source and bring the affected work into the same discussion.
Trace what depends on it
Select a node to inspect its record and status. Follow upstream prerequisites and downstream work. A missing relationship is a reason to ask the owner, rather than assume the work is independent.
Bring the evidence to planning
Use the linked context to explain which tasks can move and which must wait. Review the dependency with its owner before changing a sequence or a promised date.
A connected working example
One migration. Several connected decisions.
The Atlas example includes a schema change, a pull request, a rollback checklist and a regional cutover. A release discussion can begin with the blocking record instead of a general status update.
Pair the graph with a planning view to separate ordering from availability. A task may be ready in dependency terms while its owner is already committed to another week. Both constraints belong in the decision.
ACDFMC+1
Illustrative workspace · interactive demonstration
Inside the approach
How the model works.
The graph represents explicit relationships between records. A dependency is a recorded link, not a guarantee inferred from similar text. Missing links remain visible as missing context.
Methodology and evaluation01Work records
02Linked context
03Delivery signals
Before you move forward
A useful graph makes the source inspectable.
| Review | What to look for |
|---|---|
| Relationship | Check whether the link means blocks, belongs to, or provides context. These relationships answer different questions. |
| Source | Keep the originating record and its last known status available. A copied summary may miss a recent change. |
| Ownership | Confirm who can resolve the dependency. A linked name is useful only when responsibility is understood. |
| Missing context | Record unresolved links and unknown prerequisites before treating the visible graph as complete. |
Questions & answers
A few useful answers.
Does the graph invent dependencies?
The demonstration represents explicit links between fictional records. Similar descriptions alone do not prove that one task blocks another. Review suggested relationships before relying on them.
What should I click in the demo?
Select a task node to inspect its context, then use the zoom controls to explore the surrounding work. The detail panel stays connected to your selection.
Where does forecasting fit?
The graph explains relationships; a forecast describes a range of possible delivery outcomes. Use both to discuss whether a late prerequisite could affect the release.
Ship what you promised.
Bring the plan, the work and the next decision together.