Documentation and reference deliverables for ETOS and the Enterprise Transformation Meta‑Model (ETMM) — a single operating model that unifies the classical transformation patterns (business transformation, application modernization, brownfield discovery, greenfield development) with AI adoption — the trusted, governed enablement and human adoption of AI and agents — across the agentic SDLC, AI program digital twins, and value‑based transformation.
AI adoption is a first-class scope, not a side effect. ETOS evolves every capability and earns the trusted, sustained use of its AI by the people who operate it — advancing machine autonomy (the AI trust ladder) and human adoption (the adoption journey) together. It is as much an AI‑adoption operating model as a modernization one.
The goal is not software modernization. The goal is continuous business capability evolution. Most organizations manage projects. Projects end. Capabilities evolve continuously.
| Artifact | Audience | Format | Description |
|---|---|---|---|
ETOS_Architecture_Delivery.md |
Architects · delivery leads | Markdown | The architecture & delivery playbook in readable form, with 23 embedded diagrams and infographics. Renders directly on GitHub. |
documents/ETOS_Executive_Storyline.docx |
Exec sponsors · presenters | DOCX | Executive storyline with slide‑by‑slide structure (objective · visual · key message) and infographic recommendations. |
documents/ETOS_Adoption_Roadmap.docx |
Transformation office · delivery | DOCX | Standalone phased adoption roadmap: Crawl → Walk → Run → Fly horizons, value gates, first‑90‑days plan, operating & funding model, risks and measurement. |
All visuals embedded or referenced by the markdown live in etos-images/.
ETOS-deliverables/
├── README.md ← you are here
├── ETOS_Architecture_Delivery.md ← markdown playbook (renders on GitHub)
├── etos-images/ ← infographics + generated diagrams used by the .md
└── documents/
├── ETOS_Executive_Storyline.docx
└── ETOS_Adoption_Roadmap.docx
The markdown playbook is organized around a five‑part structure:
- A · Reference architecture — the layered platform, four engines, the enterprise knowledge graph, the ETMM meta‑model, platform services and foundation, runtime and integration.
- B · Capability model — the capability as the unit of architecture, the nine‑stage evolution journey, and enterprise citizenship as the architectural Definition of Done.
- C · Delivery model — the flywheel as an SDLC, the agentic delivery lifecycle, brownfield discovery, the F1–F13 pattern catalog and playbooks.
- D · Governance, quality & operations — trust gates, the AI program digital twin, measurement, economics, testing, and observability.
- E · Ways of working — team topology, the delivery timeline, control points (RACI), anti‑patterns, and a getting‑started checklist.
.mdrenders automatically on GitHub. KeepETOS_Architecture_Delivery.mdand theetos-images/folder together — image links are relative..docxopen in Microsoft Word, Google Docs, or LibreOffice Writer.
- Illustrative data. Pattern rankings, economic figures (the J‑curve worked example), KPIs and RACI assignments are illustrative defaults from the ETOS framework. Validate them against your own estimates and organization before adopting.
- Presentation decks. The PowerPoint decks (board briefing, architecture & delivery playbook, and infographic reference) are distributed separately and are not tracked in this repository.
- Source materials. The original prompts and source infographics are kept separately, outside this folder, as input materials.
Prepared by the Enterprise Architecture & Transformation Office.