# TD-T03: Release and readiness

Adrian Sutherland · Version 1.0 · Refreshed September 2026

© 2005–2026 Adrian Sutherland.
Source page: https://architectureportal.org/assets/technology-deployment

Map relevant questions into existing records; identify open decisions.

## Process areas

A Simple Architectural Framework (ASAF) describes four continuing areas of work.

Map the work to your actual stages and reviews. Areas may share a review or
repeat at different scopes. Keep the accepted starting point between cycles.

| ASAF process area | Question | Your activity, owner and retained record |
|---|---|---|
| Visioning | What future outcome and qualities should this change serve? | [fill] |
| Transforming | What changes, checks and handover are required? | [fill] |
| Operating | How will the result be run, supported and observed? | [fill] |
| Governing | Who accepts decisions, exceptions and any wider reconsideration? | [fill] |

## Change and identity

Name the intended change and exact package, runtime, schema and configuration.

## Compatibility and migration

Which clients, records and pending work must coexist? What changes meaning?

## Checks and exposure

What permits initial exposure, wider use and acceptance?

## Failure and recovery

Specify stop conditions, rollback compatibility, forward repair and reconciliation.

## Support and transition

Who receives the release, responds to faults and retires old versions?

## Actual results

Record actual checks and approvals alongside the expected results. Include exact versions and any findings.