# AI Release Manifest

Toolkit schema: `PAISEH-TK-1.0`
Source artifact: Chapter 10 **AI Release Manifest**

Complete `../common-artifact-header.md` first. Bind one immutable composite candidate to topology, configuration, exposure, recovery, health decisions, and actual transition receipts.

## 1. Composite Candidate Identity

| Component | Immutable identity/version | Provenance/build receipt | Compatibility and owner |
| --- | --- | --- | --- |
| Application | | | |
| AI Fit and Risk Assessment Worksheet decision | | | |
| Production Prompt Specification | | | |
| Model configuration | | | |
| Context Assembly Plan and corpus/index/source policy | | | |
| Harness Control-Loop Diagram and workflow | | | |
| Tool Permission Matrix and effective policy | | | |
| Route/runtime/policy configuration | | | |
| Evaluation Plan decision record | | | |
| AI Threat Model governance decision | | | |

- AI Operations Runbook handoff: release-health contract, effective-state identities, receipts, and recovery proof:

## 2. Target and Topology

- Environment, regions, tenants, and eligible/excluded populations:
- Topology units, state, capacity, and failure domains:
- Dependencies, isolation, and data residency:
- Assignment unit, affinity, and propagation through durable work:
- Promotion/rollback unit and reserved recovery capacity:

## 3. Configuration and Routing

- Source of truth, schema, precedence, and safe defaults:
- Approved destinations and eligibility:
- Affinity, fallback, fail-open/closed, overload, and degradation limits:
- Propagation, acknowledgement, convergence, stale-client, and drift behavior:
- Secret bindings and material scope assumptions:

## 4. Promotion and Exposure Plan

| Stage/transition | Target | Eligible/excluded population | Assignment/affinity | Min/max exposure | Observation/outcome-delay window | Advance/hold/reverse conditions | Actor/authority | Reversal path |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| | | | | | | | | |

## 5. Compatibility, Migration, and Recovery

| Changed component/state | Backward/forward compatibility | Mixed-version rule | Migration/point of no return | In-flight work | Created state/effects | Recovery action | Verification |
| --- | --- | --- | --- | --- | --- | --- | --- |
| | | | | | | | |

- Recovery-time and data-loss expectations:
- Retained snapshots/assets and cleanup duties:
- Required capacity and dependency availability:
- Latest recovery-exercise reference, result, and limitation:

## 6. Release-Health Contract

| Claim/failure | Candidate/stage | Population/denominator/slice | Signal/evidence source | Baseline/threshold/uncertainty | Window/delay | Missing/indeterminate behavior | Action/authority | Terminal result |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| | | | | | | | | |

## 7. Deployment Receipt and Closure

| Field | Actual result |
| --- | --- |
| Candidate and environment requested | |
| Effective component, route, configuration, and index identities by topology unit | |
| Transition actor, policy, start/end time, and result | |
| Population assignment and exposure achieved | |
| Configuration convergence and drift result | |
| Stage decisions and evidence references | |
| Deviations, emergency changes, owners, and expiry | |
| Recovery action and verified effective state | |
| Final steady-state or retirement decision | |
| Temporary machinery and derived-data cleanup | |
| Follow-up owners and due dates | |