ADR-004 — Transformation program area (08-Transformation) and document-type superset

Status

accepted — 2026-07-03 (decided by: kotsalidis, TPL; CEO-sponsor mandate per project brief)

Context

Prime Products Ltd has commissioned a CEO-led, company-wide, 12-month AI-first transformation. The program produces a large, coherent body of knowledge — strategy, charter, governance, requirement-analysis methodology, questionnaires, WBS, roadmap, per-department execution plans, technical blueprint, Obsidian knowledge-base blueprint, Mission Control website blueprint, KPI framework, risk register, use-case pipeline, agent registry, and a stage-by-stage commercial structure.

Alternatives considered:

1. Scatter across existing folders (plans/, 02-Requirements/, 03-Infrastructure/) — rejected: the program is one coherent domain; scattering breaks navigability and the “one home per concept” principle.
2. Use the reserved 04-Systems/ / 05-Processes/ slots — rejected: those are reserved for Prime Products’ operational systems and processes as they are captured; the transformation program is a different concern.
3. A new numbered top-level area — chosen.

The standard OKF type set (plus this vault’s requirement and interview) does not cover these document kinds; an explicit superset is needed so frontmatter stays meaningful.

Decision

1. Create 08-Transformation/ as the home of the AI-first transformation program, with numbered sub-areas: 01-strategy/, 02-program/, 03-discovery/, 04-departments/, 05-technical/, 06-knowledge-base/, 07-mission-control/, 08-ai-portfolio/, 09-commercial/. Each sub-area carries an _index.md.
2. Extend the vault’s document-type superset with: plan, framework, questionnaire, register, blueprint (in addition to the existing requirement and interview). All other frontmatter rules are unchanged.
3. Needs stated in the transformation brief are still captured as REQ-NNN files in 02-Requirements/ — 08-Transformation/ holds the program’s methods, plans, and designs, not the requirements themselves.
4. 04-Systems/ and 05-Processes/ remain reserved for as-is operational capture; discovery outputs will populate them later.

Consequences

• The vault gains one large, self-contained program area that maps 1:1 to the transformation deliverables and to the future Mission Control website structure.
• CLAUDE.md and the root README.md / _index.md must be updated in the same change to reference the new area and type superset.
• The register-style documents inside the program area (risk register, use-case pipeline, agent registry) become living documents — updated throughout the 12 months, unlike append-only ADRs.