Mission Control Blueprint — vanos.tpl.one

1. Purpose

A single pane of glass for the 12-month AI transformation, live from day one to program closure:

• Leadership (CEO, steering): where are we, what needs a decision, what is at risk — in one morning glance, on a phone.
• Project team (TPL + PRIME PRODUCTS): shared operational picture — milestones, deliverables, blockers.
• Department heads: their department’s readiness, pilots, training, and what is expected of them next.
• Stakeholders/board: credible, current, read-only reporting without slide decks.

If a status question is asked twice in a meeting, the answer belongs on Mission Control.

2. Design principles

1. Content sourced from this vault. The site renders key-account-prime markdown directly. The vault is the single source of truth; the site is a view. No double bookkeeping — nothing is authored on the site itself.
2. Update-by-commit. git push → CI build → live in minutes. Status updates are ordinary vault edits, so they are versioned, attributable, and reviewable.
3. Access-controlled. All pages behind SSO; sensitivity-tiered sections (board vs project team vs department heads).
4. Mobile-friendly for the CEO. Executive dashboard designed phone-first; everything readable without horizontal scrolling.
5. Boringly reliable. Static output, no runtime database, no server-side state to break during a board demo.

3. Recommended implementation

• Static site generator building from this repo. Recommendation: Astro (full layout control, content collections from markdown + YAML/CSV) — with Quartz as the lighter fallback if we want near-zero templating effort over an Obsidian vault. Astro chosen as primary because Mission Control needs dashboard pages (tiles, charts, role-scoped sections), not just rendered notes.
• Deployment: TPL hosting at vanos.tpl.one, behind SSO via Microsoft Entra ID (PRIME PRODUCTS is an M365 shop — users keep their work identity). Auth at the reverse proxy (e.g. oauth2-proxy/Entra) so the static site stays auth-agnostic; group claims map to role sections.
• CI/CD: push to the repo’s master → pipeline builds and deploys. Preview builds on branches for report-drafting.
• Charts from data files in the repo: KPI series, readiness scores, and budget/stage status live as YAML/CSV under a data/ path (or frontmatter tables); build-time chart rendering (static SVG) keeps pages fast and audit-friendly.
• Sensitivity guardrail: the build excludes any vault file whose frontmatter lacks a publish: mission-control flag (opt-in publishing), and never publishes data_sensitivity: high files to sections below their access tier.

Alternatives considered:

Option	Why not
Notion	Cloud SaaS, second content store → double bookkeeping, weak access mapping to Entra groups
SharePoint	Already available but poor as a program cockpit: clumsy markdown story, dashboard pages age badly, nobody visits it voluntarily
Grafana-only	Excellent for telemetry, wrong for narrative content (roadmap, decisions, meeting notes); may still back the AI-platform status tiles via embedded panels

4. User roles & access

Role	Access
CEO / steering committee	Full site, all sections
Department heads	Their department page(s) + all common sections (roadmap, training, KB progress, KPIs)
Project team (TPL + PRIME PRODUCTS core)	Full site and edit rights via git (the only write path)
Board / external stakeholders	Read-only board section only (board reporting + sanitized executive summary)

Access is enforced by Entra ID group claims at the proxy; the sitemap below notes tier per branch where it differs from “all authenticated”.

5. Sitemap

vanos.tpl.one/
├── /                          # Home — executive dashboard (phone-first)
├── /roadmap                   # 12-month roadmap, current month highlighted
├── /workstreams               # Workstream status (discovery, KB, platform, pilots, agents, training, …)
├── /milestones                # Milestone board with gate status
├── /departments/              # Index + one page per department (15)
│   └── /departments/<dept>    # Dept: readiness, pilots, training, KB coverage, actions
├── /deliverables              # Deliverable register with acceptance status
├── /ai-infrastructure         # AI platform status: deployment stage, health, usage
├── /knowledge-base            # KB progress: vault rollout, coverage % per department
├── /risks                     # Risk register view
├── /decisions                 # Decision log (ADRs)
├── /training                  # Training calendar & completion
├── /meetings                  # Published meeting notes (steering, monthly)
├── /kpis                      # KPI dashboard — program KPIs with trends
├── /process-transformation    # Process transformation tracker (as-is → to-be per process)
├── /requirements              # Requirement analysis status (REQ register view)
├── /readiness                 # Department readiness scores (matrix + trend)
├── /use-cases                 # AI use-case pipeline (funnel view)
├── /agents                    # Agent deployment tracker
├── /infrastructure            # Hardware & infrastructure status (procurement → racked → live)
├── /budget                    # Budget & stage/offer tracking        [steering + project team only]
├── /board                     # Board reporting pack                 [board tier + steering]
├── /change                    # Change management & comms updates
├── /docs                      # Documentation index (rendered vault map)
└── /archive                   # Project archive (closed phases, superseded reports)

6. Content pipeline — vault file → page

Page	Primary vault source
Executive dashboard	Aggregates below + data/kpi/*.yaml
/roadmap	../02-program/roadmap-12-month.md
/workstreams, /milestones, /deliverables	Roadmap + program status notes in 02-program/
/departments/	Department readiness + discovery notes (../03-discovery/requirement-analysis-framework.md) + data/readiness.csv
/ai-infrastructure, /infrastructure	../05-technical/architecture-overview.md + platform telemetry snapshot + hardware status data file
/knowledge-base	../06-knowledge-base/obsidian-vault-blueprint.md rollout section + coverage export from vanos-brain knowledge maps
/risks	../02-program/risk-register.md
/decisions	06-Decisions/ ADR register + program decisions
/kpis	../02-program/kpi-framework.md + data/kpi/*.yaml
/requirements	../../02-Requirements/_index.md register table
/use-cases	../08-ai-portfolio/ai-use-case-pipeline.md
/agents	../08-ai-portfolio/ai-agent-registry.md
/budget	../09-commercial/stage-offer-structure.md stage status + data/budget.yaml (placeholders until commercial data agreed)
/training, /meetings, /change, /board, /docs, /archive	Corresponding program notes, published opt-in via publish: flag

Governance link: who may publish what is governed by ../02-program/governance-model.md.

7. Update cadence summary

Cadence	What updates	Who commits
Continuous	Decisions, risks, deliverable status, meeting notes	Project team (as work happens)
Weekly	Executive dashboard data, workstream status, use-case pipeline, agent tracker, KB coverage, change updates	TPL program lead (Friday cut)
Monthly	KPI series, department readiness scores, training completion, budget/stage tracker, board pack	TPL program lead + PRIME PRODUCTS PMO counterpart
At stage gates	Roadmap/milestone gate status, stage acceptance records, archive moves	Steering (recorded by program lead)

Rule: if a page’s data owner misses two cycles, the page shows a visible “stale since ” banner — honesty over polish.