docs: present AI strategy as a diagram-first story
Build and publish Eldorado documentation / build (pull_request) Successful in 40s

This commit is contained in:
jarvis-at-skic committed 2026-10-04 12:23:41 +00:00
1 parent 7f40de708c
commit 794f2aa2d6
30 files changed
+2496 -4

No files matched your search

+21
View File
@@ -2,11 +2,28 @@
id: roadmap
title: Roadmap
description: Evidence-gated phases, no promised dates or budgets.
hide_table_of_contents: true
---
import ArchifyDiagram from '@site/src/components/ArchifyDiagram';
<div className="strategy-content">
**TO-BE · Target operating model — not installed controls or company results.**
## What must be true before widening the rollout?
Advance by exit evidence, not promised dates or usage volume. Each stage can hold, narrow or stop; changed client, data or authority boundaries reopen earlier gates.
<ArchifyDiagram name="strategy-roadmap" title="Foundation, pilot, reliable distribution, coordination and departmental expansion have exit gates" story />
- **Start bounded:** named people, lawful data handling and a reproducible baseline precede the pilot.
- **Prove recovery before coordination:** verified versions, revocation and human takeover are prerequisites.
- **Expand by department:** accepted outcomes, guardrails, total cost and experience justify continuation; sensitive decisions remain human.
<details>
<summary>Stage-by-stage entry evidence, work, exit gates and hold conditions</summary>
**TO-BE · Target operating model.** Introduction depends on the [roadmap gates](./roadmap.mdx); these pages do not describe installed controls or measured company results.
### Foundation
@@ -51,4 +68,8 @@ description: Evidence-gated phases, no promised dates or budgets.
There are no invented launch dates, budgets, staffing commitments or guaranteed gains. Phase gates permit narrowing or stopping. Re-evaluate earlier phases when the underlying client, provider, data scope or authority changes.
</details>
**Next:** [Return to the strategy destination →](./index.mdx)
</div>