---
title: Blueprint
status: draft         # draft | review | approved — only the owner sets approved
version: 0.1.0
date: YYYY-MM-DD
owner: Product Owner
---

<!-- Frozen: version 1 of this template. An artefact without `template:` is checked against it and gets a warning; new
     work uses templates/blueprint.md (version 2). Do not edit. -->

# Blueprint — Product name

<!-- Template from the UASK Engineering Hub, playbook mgmt.project-foundation, stage 5.
     Save as project/BLUEPRINT.md. How the system is structured, built, delivered and run.
     Refer to requirements by id (PRD.md) and to evidence in research/. Mark every significant or
     hard-to-reverse choice with **[ADR-NNNN]** linking to decisions/NNNN-….md. While a record has no
     number yet, mark it [ADR-candidate D1], [ADR-candidate D2], … (unique within this file); the Decisions
     stage replaces each with a link, and none is left when it closes.
     Sections marked "Optional" may be deleted; delete these comments when a section is written. -->

## System overview

<!-- A system context view (people, this system, external systems) and a container view, drawn as in
     item arch.c4-model; diagrams as code (Mermaid or similar) kept in this file. Then one paragraph on how
     responsibilities are separated. -->

```mermaid
flowchart LR
  user["User<br/>[Person]"] -->|uses| sys["Product name<br/>[Software system]"]
  sys -->|calls| ext["External system<br/>[Software system]"]
```

## Building blocks

<!-- Optional. Main modules or components, their responsibilities, and the repository layout. -->

## Data and interfaces

<!-- Optional. Data owned and its lifecycle; public interfaces, APIs, extension points, integrations. -->

## Technology stack

<!-- One row per concern; every choice that is hard to reverse links its ADR. -->

| Concern | Choice | Decision | Fallback |
|---|---|---|---|
| … | … | [ADR-NNNN](decisions/NNNN-….md) | … |

## Cross-cutting concerns

<!-- Optional. Security, privacy, performance, accessibility, observability, internationalisation,
     licensing — each tied to the NFR ids it satisfies. State the governance tier here (lightweight,
     standard or high-assurance — item mgmt.governance-tiers) with the reason; the owner chooses it. -->

## Deployment and operations

<!-- Optional. Environments, delivery path, backups and restore, rollback, monitoring. -->

## Cutover and rollback

<!-- Optional, but expected where the product replaces a running system. A sequence (flowchart or numbered
     steps), not a list of components: what is frozen or copied, what is switched in which order (addresses,
     DNS, notifications from external services, schedules), how each step is proved before the next, the point
     of no return, and how each step is undone and how long that takes. Cover every entry of the PRD's
     "External interfaces and environment". -->

## Requirements coverage

<!-- Optional, recommended. Which section covers each FR/NFR, or "deferred to Mn". -->

| Requirement | Covered by |
|---|---|
| FR-1 | … |

## Risks

<!-- What could make the plan fail, with a mitigation for each. -->

| Risk | Impact | Mitigation |
|---|---|---|
| … | … | … |

## Implementation sequence

<!-- Numbered steps from the first approval to the first release; the roadmap's milestones follow them. -->

1. Owner approves this blueprint and the proposed ADRs.
2. …
