# BP-V08 (Runtime and recovery)

Adrian Sutherland · Version 1.0 · September 2026

© 2005–2026 Adrian Sutherland.

Refreshed for the September 2026 website update.

Licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Keep the [edition note](https://architectureportal.org/downloads/blueprint/1.0/edition.md) with adaptations.

- Question: Accepted work must survive the relevant failure.
- Design state: SOFT-01 (Later software option)
- Level: Logical
- Design: Proposed; checks unrun
- Scope: Release packaging, persistence and recovery responsibilities
- ASAF aspects: Technology, Systems, Security, Management
- View page: /blueprint/technology-operation
- Editable source: runtime.mmd
- Export: runtime.svg

## Reading the view

The staff client calls the application. Its case handler uses a durable transactional store; the notification worker resumes committed work. Identity and booking have separate dependencies. Recovery copies can restore older records, so accepted business work may need reconciliation before writes resume. Runtime products, instance counts and service objectives remain open.

## Key

- The application group shows release packaging. The recovery group shows restoration and reconciliation.
- A recovery copy is not proof that all accepted work can be restored; reconcile the missing interval.

## Linked records

- [TD-D1 (Runtime arrangement)](/blueprint/objects#td-d1)
- [TD-R1 (Recovery procedure)](/blueprint/objects#td-r1)
- [TD-C1 (Release and compatibility)](/blueprint/objects#td-c1)
- [TD-V1 (Environment checks)](/blueprint/objects#td-v1)
- [SO-R1 (Readiness record)](/blueprint/objects#so-r1)
- [SO-A1 (Service acceptance)](/blueprint/objects#so-a1)
- [SO-I1 (Incident and restoration)](/blueprint/objects#so-i1)

The view page supplies the decisions, open choices and checks. The object
reference supplies each identifier's meaning and source.