Context graph
The context graph connects facts to the tasks, people and approvals that depend on them. It helps answer what a change affects and who needs to act next.
The relationship is often more useful than the fact on its own. A new date matters because another activity or decision depends on it.
Trace a changed date
Suppose training moves from Wednesday to Friday, while a readiness review remains scheduled for Thursday. The change affects the review agenda, the sign-off decision and any customer update based on those dates.
Training has moved to Friday. Identify the activities and approvals that depend on it, show the sources, and prepare an update for the owners. Keep any unconfirmed dates marked as targets.
A good result identifies the dependency and next owner, rather than simply repeating the new date.
Separate progress from authorization
| Fact | What still needs checking |
|---|---|
| Code is merged | Whether the release has passed its required review. |
| Training is complete | Whether the owner has approved readiness. |
| A proposal is drafted | Whether scope and commercial terms are accepted. |
One step being complete does not establish that every dependent condition has been met.
Review the proposed next step
Check that Milo has connected the correct project, owner and approval. If a relationship is uncertain, ask for the source or confirm it with the responsible person.
The context graph is part of the enterprise context foundation. Start with the sources that establish a relationship: the project record, the responsible owner and the decision that governs the next step.