29 lines
2.1 KiB
Plaintext
29 lines
2.1 KiB
Plaintext
---
|
|
id: skills-maintenance
|
|
title: Skills maintenance
|
|
description: Review, drift, deprecation, rollback and incident handling.
|
|
---
|
|
|
|
|
|
<div className="strategy-content">
|
|
|
|
**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.
|
|
|
|
Data & AI reviews catalog health with the owning teams. Quality Engineering samples accepted outputs and adds confirmed failures to regression sets without exposing sensitive content. Platform & IT watches unsupported, deprecated and revoked revisions and tests distribution recovery. Architecture & Security reviews emerging misuse and exception expiry. Remove redundant or unused entries deliberately, after examining whether poor discoverability or fit explains non-use.
|
|
|
|
A reported unsafe behavior opens an incident with artifact, policy and client versions. Architecture & Security coordinates containment; Platform & IT revokes authority, stops scheduling and quarantines affected revisions; the owning department handles customer or business consequences; Quality Engineering reproduces the failure; Data & AI coordinates catalog correction and trend analysis. Preserve minimal restricted evidence and involve People & Administration Squad for employee-data concerns and Finance & Accounting Squad for financial effects. Restart requires a reviewed fix, regression evidence, verified rollback/revocation and accountable human authorization. Closing the incident does not erase the historical failure from measurement.
|
|
|
|
## Proposed maximum review intervals
|
|
|
|
Owner ratification is required before adoption. Review earlier after incidents or material dependency changes.
|
|
|
|
| Tier | Maximum days between substantive reviews |
|
|
| --- | --- |
|
|
| R1 | 90 |
|
|
| R2 | 60 |
|
|
| R3 | 30 |
|
|
|
|
</div>
|