PRIME PRODUCTS · MISSION CONTROL
AI-first transformation · by TPL · vanos.tpl.one

Docs / 08-transformation/02-program/epic-board

Epic board

Program progress by epic against the original plan — agent-refreshed register with an append-only deviations log (REQ-012, ADR-009).

type: register updated: 2026-07-15 owner: taranas

Epic board — progress vs the original plan

One row per epic: the roadmap’s 13 phases (P0–P12) plus the pre-program commercial phase. The Baseline column is frozen (it mirrors the roadmap and only changes with a formal re-baseline); everything else is maintained by the board-refresh agent — nightly and on demand — from the HANDOFF, session logs, and the vault (ADR-009). M1 ≈ September 2026 (assumption, pending kickoff confirmation).

Status legend: not-started · in-progress · on-track · at-risk · done.

Epics

EpicTrackBaselineStatusProgressLatest
PRE — Commercial & kickoffFoundationspre-M1 (Jul–Aug 2026)in-progress70%Stage-1 offer drafted, priced and discounted; awaiting TPL C-suite review, then issue to Prime Products
P0 — Preparation & governanceFoundationsM1in-progress20%Charter, governance model and board outline drafted; CEO sign-off pending
P1 — Discovery & requirementsFoundationsM1–M3in-progress20%Method + 5 questionnaires ready; REQ-001…014 captured; pilot clarification call held (cylinders dept) validates the interview approach — general department discovery not yet started
P2 — Process map & AI opportunitiesFoundationsM2–M4not-started0%Method defined in discovery framework; waiting on discovery
P3 — Infra architecturePlatformM2–M3in-progress10%Technical blueprint drafted (assumption-flagged); site survey pending
P4 — Hardware procure & deployPlatformM3–M6not-started0%Gated by board budget approval (target end M2) and HQ server-room survey
P5 — LLM stack implementationPlatformM4–M7not-started0%Stack chosen in blueprint (vLLM, Qdrant, n8n; Llama-3.3-70B + Krikri-8B)
P6 — Obsidian KB design & rolloutKnowledge & VisibilityM2–M9in-progress15%Vault live with conventions and program docs; raw-source layer + automated ingest pipeline shipped (ADR-012/013); first Prime Products department profile captured (cylinders)
P7 — Mission Control siteKnowledge & VisibilityM1–M12on-track50%Live ahead of baseline at vanos.tpl.one behind Access — nav regrouped into dropdowns as page count grows; still doubles as the pilot’s working dashboard, plus docs, graph (growth-replay timeline), tasks, wiki-chat, board
P8 — Department pilotsValue DeliveryM6–M8in-progress25%Pilot offer priced, pending TPL C-suite review; first sample order-email batch (6 of 20–50) received and fully distilled, revealing the four-tier order-brokerage chain and a hard mailbox-ingestion constraint — still awaiting the team-details handoff and remaining sample volume
P9 — Agents & automationValue DeliveryM7–M10not-started0%Use-case pipeline + agent registry drafted
P10 — Training & change mgmtValue DeliveryM4–M11not-started0%Change/training plan drafted
P11 — Full rolloutValue DeliveryM9–M11not-started0%
P12 — Optimization & governanceValue DeliveryM11–M12not-started0%

Deviations from baseline

Dated, append-only. Only real changes against the original plan (scope, timing, cost) — not routine progress.

  • 2026-07-03 — Cost (PRE): Stage-1 fixed fee changed €69,500 → €59,075 (15% program-launch discount), payment split 40/60. Source: offer TPL-PRIME-2026-001.
  • 2026-07-03 — Scope (P7): Wiki-chat added — conversational access to the knowledge base on the Mission Control site (REQ-011/ADR-008: Bedrock Opus 4.6, no retrieval DB, OKD-hosted). Not in the original WBS; delivered same day.
  • 2026-07-03 — Timing (P7): Mission Control delivered ahead of baseline — v1 live pre-M1 (baseline had v0 launching in M1).
  • 2026-07-02 — Timing (P6): Knowledge-base vault bootstrapped pre-M1 (baseline start M2) — program docs already live in it.
  • 2026-07-03 — Assumption (all): program start month still unconfirmed — M1 ≈ September 2026 pending CEO sign-off; all calendar dates shift with it.
  • 2026-07-06 — Timing (P8): Pilot work started pre-M1 — department selected (cylinders/email-order desk), REQ-014 captured and validated, and the CEO clarification call held and ingested. Baseline had pilot department selection at M4 and pilots launching M6–M8.
  • 2026-07-06 — Scope (P6): Raw source layer (raw/) and an automated ingest pipeline added (ADR-012/013) — source material (e.g. call transcripts) is committed for provenance and auto-distilled into the wiki via a detect → distill → PR flow. Not in the original WBS.
  • 2026-07-11 — Cost (P8): First pilot wave priced — €51,000 fixed fee (15% program-launch discount applied), payment split by phase. Baseline Stage 7 pricing was an unset placeholder. Source: offer TPL-PRIME-2026-002.
  • 2026-07-15 — Assumption (P8): First sample order-email batch (6 of 20–50 requested) received and fully distilled — reveals Prime’s order-entry process as a four-tier email brokerage chain (customer/shipowner-manager → Prime → manufacturer → port agent) with two deterministic quote↔order match keys, but confirms a hard technical constraint: the M365 search connector cannot expose nested email-attachment content, so automated mailbox ingestion needs full Graph API attachment access (or IMAP/EWS) plus PDF/OCR extraction, not the connector path originally assumed. Source: discovery note.