---
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

**Entry evidence** — Strategy scope accepted for planning; existing teams identified.

**Work** — Inventory actual client hosts/builds, provider/data terms, repositories, authority, owners and event availability; select low-risk workflows and metric definitions.

**Exit evidence and hold condition** — Named accountable people and independent reviewers, bounded pilot charter, forbidden actions, data/retention decision and reproducible baseline plan. Hold if accountability or lawful collection is unresolved.

### Governed skills pilot

**Entry evidence** — Foundation evidence approved; no privileged autonomous effects.

**Work** — Build a small registry, immutable contract, client adapters, evaluations, coaching and synthetic measurement verification.

**Exit evidence and hold condition** — Qualified client/skill tuples, mandatory safety checks, independent task acceptance, reconciled coverage and user feedback. Hold or narrow scope if quality or data coverage is inadequate.

### Reliable distribution

**Entry evidence** — Pilot quality and usefulness support continuing.

**Work** — Canary updates, effective-version readback, version locking, exception expiry, stale/offline handling and rollback.

**Exit evidence and hold condition** — Tested revocation and recovery, no bypass of central privileged gates, owners can support the catalog. Hold if effective versions or controls cannot be verified.

### Logical SDLC coordination

**Entry evidence** — Distribution, authority and measurement evidence stable.

**Work** — Observe and assemble evidence first, then propose and route work within scoped identities and budgets.

**Exit evidence and hold condition** — Exact-artifact approvals, idempotency, duplicate/outage recovery, separation of duties, audit and kill-switch drills pass; humans can take over. No authority expansion based on usage alone.

### Departmental expansion

**Entry evidence** — Each department supplies a workflow owner, outcome, data boundary and capacity.

**Work** — Add Operations, Marketing, Finance & Accounting and HR & Administration workflows with domain-specific review; Product and Technology continue quality improvement.

**Exit evidence and hold condition** — Departmental accepted outcomes, guardrails, total cost and experience justify continuation; sensitive decisions stay human. Stop or roll back workflows without adequate evidence.

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 →](./target-operating-model.mdx)

</div>