$ agit // control plane
Scenario for the lead specialist · Altered Graph.it

The truth about the project — and how to land it with leadership

You can see the project drifting. How do you show it to leadership in a language they'll hear?

AG.it gives the engineer a precise picture: the goal graph and critical path, an atomic diff between snapshots, plan health, time-travel. Every read carries the evidence you can take upward — and a translation into the money and decisions the owner hears.

“Project state is computed from facts — and the interface proves it.”

Who this is for, and why

Lead engineer · tech lead · the person who owns the outcome and influences leadership

Sees the real state before anyone, but their “the graph says we're in trouble” loses to “80% done” in the report upstairs. Wants a tool that gives the technical truth AND translates it into money/risk — so the owner or leadership makes the right call (and buys the system).

The pain they pay to remove

The truth isn't heard
“Critical path at risk” loses to “80% of tasks closed”. Leadership looks at percentages, not the graph.
Nothing to prove it with
To justify “move the deadline / add people” you need dated facts, not feelings.
Status distorts upstream
By the time it reaches the owner, “stuck on the integration” becomes “all on track”.
Manual report assembly
Instead of engineering — collecting status from people for every meeting.

What they get

Graph and critical path
You see which node holds the outcome and what cascades behind it — not a flat task list.
Atomic diff
Exactly what changed between snapshots — by field (deadline: was → now), not “changed”.
Time-travel
Any date is reconstructable from snapshots — prove when and what slipped.
Translation into money
The same graph shows money at risk — the language the owner speaks.

From technical truth to a leadership decision

Using “CRM rollout at Mercury Trade”: the critical path hit an acceptance milestone — here's how to turn that into an argument for the owner.

Step screenshots show the detailed (expert) view. The live demo opens in the lightweight focus mode: the full toolset is one tap away — “expert” on the bottom dock or the F key.

1
Step 1 · Project → Goal map

The goal graph and the critical path

altered-graphit.com · Project → Goal map
The goal graph and the critical path
What the engineer sees

Goals by phase with dependencies; the critical path and blocked/at-risk nodes highlighted. Zoom and pan for big graphs.

How it helps

You immediately see which node holds the finish and what cascades behind it. That's the basis for “here's the bottleneck”, not “things are a bit late”.

2
Step 2 · Project → History → What changed

An atomic diff between snapshots

altered-graphit.com · Project → History → What changed
An atomic diff between snapshots
What the engineer sees

A diff of two snapshots: achieved / slipped / new risks, and per task the exact field change (deadline: May 15 → May 30). Plus a signal lane (what happened between snapshots).

How it helps

Exact dated facts instead of feelings — ready material to justify a deadline or scope change.

3
Step 3 · Project → Plan health

Plan health: where it's broken

altered-graphit.com · Project → Plan health
Plan health: where it's broken
What the engineer sees

Left — observations and plan structure (tasks with no deadline, no links). Right — specific anomalies and tasks in focus. Every item drills to a specific task.

How it helps

You see not just “what's wrong” but which tasks exactly — you can open the task card and point.

4
Step 4 · Project → As of (time-travel)

Rewind two weeks — and show the drift

altered-graphit.com · Project → As of (time-travel)
Rewind two weeks — and show the drift
What the engineer sees

“2 weeks ago → now”: the state on the chosen date is rebuilt from snapshots. You see how it was then and how it diverged from plan by today.

How it helps

Proof of drift over time — can't be written off as “intended”. A strong argument at retro and upstairs.

5
Step 5 · Project → Tasks (working state)

Working state and backlog

altered-graphit.com · Project → Tasks (working state)
Working state and backlog
What the engineer sees

Columns Shipped / In progress / Stuck and a collapsible Backlog — grouped by goal with a “+N more” counter. All computed from the snapshot, not hand-maintained.

How it helps

An honest operational picture of the team; you see what's stuck and how much sits in the backlog — without a separate board.

6
Step 6 · Project → History → Log & console

Event log + console (REPL)

altered-graphit.com · Project → History → Log
Event log + console (REPL)
What the engineer sees

History on the left — snapshots and acceptances with dates. On the right, the agit console: the log command prints a clickable history; you can jump to any snapshot (checkout) or record an acceptance.

How it helps

An append-only log: entries aren't edited — changes are added as a new event. An engineer's tool that doubles as the evidence base.

7
Step 7 · Project → Overview (for leadership)

Translation into money for the owner

altered-graphit.com · Project → Overview (for leadership)
Translation into money for the owner
What the engineer sees

The same project in money terms: the “money at risk” verdict, the revenue path, the Revenue / Backlog / At-risk split. The Manager / Engineer perspective toggle lives in the global header.

How it helps

A ready screen to bring to the owner: the technical truth translated into money and one decision. You're the champion — and you have what it takes to convince.

8
Step 8 · How to start

First technical snapshot in ~10 minutes

altered-graphit.com · How to start
First technical snapshot in ~10 minutes
What the engineer sees

Import a task snapshot from Jira / Excel (CSV or XLSX) — state builds at once; add the goal graph later. There's a tasks-only mode to start.

How it helps

You can stand it up on your project in an evening and bring leadership not an idea but a working picture on real data.

What changes for the lead specialist

BeforeAfter
“The graph is bad” loses to “80% done”Critical path and money at risk — visible and provable
Nothing to justify a re-planAtomic diff and time-travel give dated facts
Status distorts upstreamOne and the same fact — for the engineer and the owner
Manual status gatheringState computed from the snapshot automatically
Stand up your project, rewind a couple of weeks, open the money view — and bring it to the owner or leadership. It's a conversation in their language, backed by your facts.

Terms

Snapshot — a snapshot of tasks on a date; state is computed from it.
Critical path — the chain of goals that sets the deadline: a slip in any one moves the finish.
Atomic diff — a per-field change between snapshots (deadline: was → now).
Signal — a recorded event between snapshots (note, acceptance, re-estimate).
Acceptance confirmation — a record of an accepted milestone in the log — with a date and a basis.
checkout — jump to the state at a chosen snapshot (time-travel).