Timeline and projections
Projections show how your goals move your scores over time, with every number traceable to its inputs.
Last updated September 22, 2026
A timeline lays your goals and milestones against dates. Projections take the next step and estimate how your scores will move as those goals are met, so you can see the payoff of a plan before you fund it.
The Trajectory chart draws this as lines over time. Each line, your overall Pytheus Score plus one per domain, runs from where you were, through where you are now, and on to where you are headed: its target by the deadline. Click any line for that domain's were, now, and headed, or switch to the Gantt timeline to see the milestones producing the movement.
Projections come from Pytheus Intelligence. They are deterministic, which matters more than it sounds: the same goals, targets, and dates always produce the same projected scores. Nothing is estimated by a model that drifts between runs. If a projected number changes, an input changed, and you can trace it. Modeled figures are labeled as modeled.
What the projection reflects:
As a capability's maturity rises toward its target, its domain score rises, weighted by criticality.
Domain movement rolls into your Org Score, the criticality-weighted maturity across in-scope capabilities.
Org Score is half of your Pytheus Score. Meeting committed milestones also feeds goal alignment and execution discipline, so disciplined delivery lifts the headline beyond the maturity gain alone.
A projection is the effect of completing the goals you set, on the dates you set. It is a planning instrument, not a promise. Slip a milestone and the deterministic engine simply recomputes against the new dates.
Use projections to compare plans. If two roadmaps cost the same, the one with the larger projected Org Score movement is closing higher-priority gaps. Sequence the driving work first with planning horizons.