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: skills-maintenance
title: Skills maintenance
description: Review, drift, deprecation, rollback and incident handling.
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 happens when a skill drifts or causes harm?
Monitor usefulness and safety throughout a revision's life. Unsafe behavior triggers containment; a correction returns through independent tests and approval, never automatic reinstatement.
<ArchifyDiagram name="strategy-maintenance" title="Monitor, triage and test corrections; promote safely or contain and roll back" story />
- **Named ownership:** Data &amp; AI coordinates catalog health with the owning teams.
- **Early triggers:** incidents and client, model or dependency changes override the calendar.
- **Recovery is verified:** rollback restores a known-good bundle; it cannot undo disclosure or past effects.
<details>
<summary>Review responsibilities, incident handling and proposed review intervals</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.
Every approved skill has an accountable owning team, independent reviewer, review due date, supported client matrix and rollback bundle. Review both usefulness and safety, not just metadata freshness. Proposed maximum review intervals are recorded by risk tier; incidents, dependency changes, model/client drift or repeated failures trigger earlier review.
@@ -25,4 +42,8 @@ Owner ratification is required before adoption. Review earlier after incidents o
| R2 | 60 |
| R3 | 30 |
</details>
**Next:** [Use exit evidence to choose the next rollout stage →](./roadmap.mdx)
</div>