# Permadyn AI: sample release review

Blank planning template. This is not a completed assessment or certification.
Agree the checks, thresholds, owners, and evidence required for the specific project before implementation.

## Release identity
- Application and workflow:
- Version / commit / deployment environment:
- Model, provider, model version, and configuration (if applicable):
- Reviewer, decision owner, and review date:
- Scope, exclusions, and known limitations:

## 1. Does it do the job?
- Representative tasks and expected outputs:
- Current process baseline and how it was measured:
- Quality criteria, test set, review method, and acceptance thresholds:
- Observed results, errors, omissions, and unsupported answers:
- Human review steps and escalation rules:
- Latency, throughput, recurring cost, and measurement conditions:
- Evidence location and unresolved issues:

## 2. Does it respect access?
- Permitted data sources and data movement:
- Role-by-role read and action permissions:
- Denied-access and cross-user isolation checks:
- External services, retention settings, and approved outbound requests:
- Secret storage, account ownership, and log contents:
- Evidence location and unresolved issues:

## 3. What happens when it fails?
- Integration timeouts and unavailable dependencies:
- Retry behavior and duplicate-request handling:
- Invalid inputs and incomplete outputs:
- Monitoring signals, alert recipients, and escalation path:
- Backup restore, rollback steps, and rehearsal results:
- Person authorized to stop or roll back the release:
- Evidence location and unresolved issues:

## 4. Who runs it after launch?
- Source-code rights, accounts, configuration, and documentation:
- Deployment and operating instructions:
- Third-party licenses and recurring costs:
- Maintenance owner, update process, and model change checks:
- Support scope, hours, response terms, and exclusions:
- Handoff participants and open actions:

## Acceptance decision
- Accepted / accepted with agreed conditions / further work required:
- Conditions, owners, and due dates:
- Decision owner and date:

Keep completed reviews and sensitive evidence in the agreed project repository.