One feature three roles with VectorGraph in practice

Maya picks up ENG-2189 from Sprint 14, a bulk-archive workflow for ops teams. Instead of reading the spec, the Signal, and the linked PRs in three tabs, she runs vectorgraph north plan --issue ENG-2189 and gets a compact brief: which files to read first, which symbols her change will touch, which routes and tests sit at risk, and which evidence is still missing. She writes the change, opens a PR, and the NorthGraph verdict lands as a comment within seconds, clean, medium risk, three effect classes added, all under policy.

1. 01

   Sprint planning showed the issue with its impact already attached, 3 routes, 14 symbols, 28 tests.

2. 02

   vectorgraph north plan returned the implementation brief and the spec doc, permission-filtered to her scope.

3. 03

   PR opened; NorthGraph verdict posted as a comment with the effect breakdown and any missing tests.

4. 04

   Reviewer approves; merge triggers the deploy marker that auto-closes ENG-2189 and notifies the originating customer.

David sees a Slack thread from Karri at acme.co: customers cannot tell which migration steps are safe to run before Friday's cutoff. He reacts with the configured emoji and the message becomes SIG-441 with the permalink intact. Before triage, he asks a scoped AI agent for a product brief. The agent summarizes the customer pain, affected accounts, success metric, open risks, suggested acceptance criteria, and roadmap impact from the Slack thread, prior Signals, project docs, and linked decisions. David reviews the brief, triages SIG-441 into the Migration readiness project, and turns the agent draft into final acceptance criteria. The roadmap updates to show the new migration readiness dependency and the milestone at risk. He maps the customer journey on the project's Canvas, then pulls ENG-2189 into Sprint 14. By the demo, the milestone closes, the roadmap risk clears, and the parent Initiative, ops workflow modernization, advances from 71% to 78%.

1. 01

   Captured from Slack into Signal in two clicks; sender attribution preserved.

2. 02

   Scoped AI agent drafts the product brief, acceptance criteria, risks, and roadmap impact from permission-filtered context.

3. 03

   Roadmap and sprint views show the dependency, milestone risk, project completion, and NorthGraph callouts without a spreadsheet.

4. 04

   Milestone closes automatically when its issues ship; the roadmap risk clears; Signal originators get the close-the-loop email.

Karri wants to know whether ops workflow modernization is on track before the leadership review. In two clicks, he creates a saved view for the top-level Initiative: linked projects, milestones, roadmap dependencies, open risks, customer Signals, owner updates, shipped issues, and verification evidence. The view shows 78% progress, one milestone closed Friday, two dependencies at risk, and three customer Signals still waiting for close-the-loop updates. He filters to risks, sees the blocked migration-readiness dependency, the owner, and the next decision needed. Then he asks a scoped AI agent to draft the executive update from the Initiative activity, roadmap changes, and linked evidence. Karri reviews it, shares the view with leadership, and walks into the review knowing what shipped, what is blocked, and what needs escalation.

1. 01

   Creates a saved Initiative view in two clicks, scoped to progress, risks, milestones, owners, and customer Signals.

2. 02

   Filters to at-risk work and sees the blocked dependency, owner, due date, and related evidence without opening a spreadsheet.

3. 03

   Scoped AI agent drafts the executive update from Initiative activity, roadmap changes, and linked verification evidence.

4. 04

   Leadership gets one shared view of progress, risk, shipped work, and escalation decisions.