---
title: Architecture review scope — [system]
status: draft        # draft | agreed
version: 0.1.0
date: YYYY-MM-DD
owner: [decision owner]
---

# Architecture review scope — [system]

<!-- Playbook arch.architecture-review, stage 1, rule R1. One page. The decision owner agrees it before any
evidence is gathered. Replace every [bracketed] value; delete these comments when the scope is agreed. -->

## Review

| Field | Value |
|---|---|
| Review id | AR-YYYY-MM-[system] |
| Variant | [own product / inherited system / proposed design / documents of a design under construction] |
| Decision owner | [name, role] — agrees this scope, ranks scenarios, decides on findings |
| Reviewer | [person or agent] |
| Independent reviewer | [person or separate agent session] — re-checks Critical and High findings (R13) |
| System experts | [maintainers, hosting provider, client staff] |
| Report goes to | [names] |
| Timebox | [n] days, from YYYY-MM-DD to YYYY-MM-DD |
| Planning horizon | [until release X.0 / six months / before a launch: until the launch plus [n] weeks of observation] — the horizon for the likelihood in severity (R7) |
| Scope status | [agreed by the decision owner on YYYY-MM-DD / taken from the brief [link], not confirmed by the decision owner — missing fields filled with the defaults stated here] (R1) |

## Question and decision

<!-- One question the review answers and the decision that waits for the answer. A review without a decision
behind it turns into an opinion survey. -->

- **Question:** [Can the shop be upgraded to platform version N without a rebuild?]
- **Decision it informs:** [upgrade in place, or quote a rebuild]
- **Known business goals and constraints:** [budget, deadline, regulations, hosting limits]
- **Known concerns:** [what prompted the review]

## System and boundary

- **In scope:** [systems, containers, environments — for example production and staging web shop, database, payment
  and delivery integrations]
- **Out of scope:** [for example visual design (see HIF), content, third-party SaaS internals]

## Inputs and access

<!-- Read-only access only (R2). Each input becomes one or more evidence ids during stage 2. -->

| Input | Where | Access | Granted by | Status |
|---|---|---|---|---|
| Repository | [URL] | read | [name] | [requested / works] |
| Decision records, blueprint | [path] | read | | |
| Copy of files and database | [how the copy is taken without touching the live system] | read | | |
| Hosting or control panel | [provider] | read-only user | | |
| Logs and metrics | [where] | read | | |
| Interviews | [who] | written answers | | |

## Permissions and handling

- **Live system:** read-only (R2). Active testing permitted: [no / yes — what, when, written permission reference].
- **Secrets:** stored only in [the project's secret store]; never in the report, issues or chat (R11).
- **Personal data:** [present / not present] in copies; copies kept at [where], deleted on [date].

## Agreement

| Decision owner | Date | Note |
|---|---|---|
| [name] | YYYY-MM-DD | [agreed / agreed with changes] |
