---
template: prd/2
title: Product Requirements
status: draft         # draft | review | approved — only the owner sets approved
version: 0.1.0
date: YYYY-MM-DD
owner: Product Owner
tier: standard        # lightweight | standard | high-assurance — the owner decides (mgmt.governance-tiers); the reason is in the Blueprint
---

# PRD — Product name

<!-- Template from the UASK Engineering Hub, version 2, playbook mgmt.project-foundation, stage 3.
     Save as project/PRD.md. The front matter says which tier the project is on. A section opening with
     "Required: <tiers>" is required at those tiers only; "Optional" means never required; no marker means required
     at every tier. Delete these comments when a section is written. The earlier version is
     templates/prd-v1.md; a PRD without `template:` is checked against it and gets a warning. -->

Keywords MUST, SHOULD, MAY follow [RFC 2119](https://www.rfc-editor.org/rfc/rfc2119) /
[RFC 8174](https://www.rfc-editor.org/rfc/rfc8174). Ids (`S-…`, `FR-n`, `NFR-n`, `AC-n`; outcomes are `O-n` in
the vision) are stable, never reused, and referenced from the blueprint, roadmap, issues and tests.

## Problem

<!-- Who has which problem today, and what it costs them. Two to five sentences, no solution yet. -->

## Users and context

<!-- Optional. User groups, their environment and devices, existing systems the product lives next to. -->

## Scenarios

<!-- End-to-end situations the product must handle; each serves at least one vision outcome, named in the
     last column. Every outcome of the vision must appear there at least once. -->

| ID | Scenario | Actor | Inputs | Result | Outcome |
|---|---|---|---|---|---|
| S-A | … | … | … | … | O-1 |

## Functional requirements

<!-- One testable statement per row; cite the scenario. Priority is must, should or could (what is dropped first
     when the appetite runs out). State is for a product that is already partly or fully built (done, partly,
     not started, waiting), so that the table also shows what is left; for a new product write "not started". -->

| ID | Requirement | Scenario | Priority | State |
|---|---|---|---|---|
| FR-1 | The system MUST … | S-A | must | not started |

## Non-functional requirements

<!-- Quality requirements with measurable targets. Name the characteristic in the nine words of ISO/IEC 25010:2023
     (item arch.quality-attributes#R1): functional suitability, performance efficiency, compatibility, interaction
     capability (accessibility belongs here), reliability, security, maintainability, flexibility, safety.
     "Fast" is not a requirement; "p95 page load under 2 s on <device>" is. Say how each is checked (a test, a
     monitor, an inspection or a review). Recovery, rollback, monitoring and support dates go in "Operability"
     below. -->

| ID | Characteristic | Requirement | Checked by |
|---|---|---|---|
| NFR-1 | … | … | … |

## Acceptance criteria

<!-- Checks that decide whether the release is accepted; each names the ids it proves. Each also states how it
     is performed: the method, the environment where it can really be performed, the expected result (a number
     or an observable state, not a distribution) and who performs it. Check that it can be performed in that
     environment: a criterion that needs real personal data on a test site, or two outcomes that cannot happen
     together, is a defect of the criterion. Example:
     - [ ] AC-3 Card payment completes (proves FR-7). Method: test card, sandbox of the payment service;
       environment: test site; expected: order status "paid" within 60 s; performed by: owner. -->

- [ ] AC-1 …

## Constraints and assumptions

<!-- Optional. Fixed givens (platform, hosting, budget, deadline) and unverified beliefs; each assumption
     gets a planned check. -->

## Parity with the current system

<!-- Optional. For a re-foundation of a running product: one table of what already works instead of dozens of
     requirements. Write requirements only for what changes, what is at risk and how the switch is made. -->

| Capability | State | Evidence |
|---|---|---|
| … | done / partly / not started | … |

## External interfaces and environment

<!-- Required: standard, high-assurance — and at any tier where the work replaces, migrates or rebuilds a running
     system (playbook mgmt.project-foundation, R12). List everything outside the system that depends on it or on
     its hosting, and end each entry as a requirement or acceptance criterion, or as a decision to drop it. Walk the
     list: public addresses and redirects (including with and without "www", http and https, rewrite files); feeds
     and sitemaps consumed by others; webhooks and notification addresses of payment, delivery and other
     services; consumers of any API; scheduled jobs; settings kept in the hosting panel (language version and
     handler, limits, mail routing); DNS records and certificates; outgoing mail and the services that depend
     on it; copies and backups kept outside the host; accounts and keys held by third parties. The Blueprint's
     section 3 carries the same inventory with a contract or an owner for each. -->

| Interface or setting | Today | After the switch | Who owns it | Covered by |
|---|---|---|---|---|
| … | … | … | … | FR-n / AC-n / dropped |

## Operability

<!-- At every tier — what the people who run the system need, as values (item
     arch.quality-attributes#R8, playbook mgmt.project-foundation, R13): a number, a date, a named owner, or "none"
     with the reason. Derive each value from what the stakeholders can bear, not from what the hosting offers; where
     a value is a guess, say so and name the check that settles it. At the lightweight tier, "none" with a reason is
     enough for a point that does not apply, but a system that holds data the business cannot recreate still states the
     recovery point, the recovery time and the restore test (playbook mgmt.project-foundation, R13). The Blueprint's
     section 7 says how each value is met. -->

| Point | Requirement (value) | Checked by |
|---|---|---|
| Availability | the target and the hours it applies to | … |
| Recovery point (RPO) | how much data may be lost | … |
| Recovery time (RTO) | how long until it is back | … |
| Restore test | how often, by whom, and the date of the last proof | … |
| Rollback | how a release is undone and how long that takes | … |
| Monitoring | what is watched and who is told | … |
| Who runs it | the person or team, and the cover | … |
| End of life | the end-of-support date of each runtime and platform, and the plan | … |

## Sources and traceability

<!-- Optional. Where each requirement came from: the client's brief, a numbered clause of a specification, an
     owner decision with its date. Needed when requirements are derived from client material or earlier
     decisions rather than invented. -->

| Requirement | Source |
|---|---|
| FR-n | … |

## Out of scope

<!-- What this release will not do, following the vision's non-goals. -->

- …

## Open questions

<!-- Optional. Each question names who answers it (owner, client through the owner, technical lead, an expert of
     the existing system) and by when. -->
