Roadmap

Value in weeks, not quarters. Most of the code already exists in the demo.

flowchart LR
  P0[Phase 0<br/>Foundations<br/>DONE] --> P1[Week 1<br/>MVP - 1 project]
  P1 --> P2[Week 2<br/>Drift report]
  P2 --> P3[Weeks 3-6<br/>All 4 projects]
  P3 --> P4[Weeks 6-10<br/>Ask-the-runbooks]
  P4 --> P5[Ongoing<br/>Improve]

Phase 0 — FoundationsWeek 1 — MVPWeek 2 — Drift reportWeeks 3–6 — All four projectsWeeks 6–10 — Ask-the-runbooksOngoing — Improve

already built

Wiki IA, provisioning/decomm/P1 templates, CI validators, Ansible + SharePoint + Power BI + Teams adapters, drafter, drift report, Azure OpenAI provider — runnable in the demo today.

Create the Code wiki + service account. Add a git.push hook on one Ansible repo → n8n → Azure OpenAI → PR. First live auto-drafted runbook.

Nightly coverage/freshness report to a Teams channel. Turns invisible doc-debt into a number that trends down.

Onboard the remaining repos (config only). Per-project classification; China content stays in-region with summaries + links.

Index the curated wiki (Azure AI Search Basic or pgvector). Teams assistant answers with citations and ACL trimming. +$0–75/mo.

Tune prompts, grow the corpus, add sources (SNOW, SolarWinds) when they earn their place.

What we need from stakeholders

• Sponsor + budget sign-off (~$30–50/mo, no new infra).
• Endorse PR-gated publishing (automation never merges).
• A Code wiki + service account in the ADO org.
• A named owner per top-level section.
• Confirm Entra ID group model for later ACL trimming.