# Blueprint outline

Adrian Sutherland · Version 1.0 · September 2026

© 2005–2026 Adrian Sutherland.

Refreshed for the September 2026 website update.

## Identity

- Subject and purpose:
- Intended users and decisions:
- Owner and decision authority:
- Edition and date:
- Source history and notices:

## Scope and design states

- Included work and people:
- Exclusions and open responsibilities:
- Current arrangement, proposed increments and alternatives:
- Conceptual, Logical and Physical detail needed:

## Views

| View ID and name | Question | Design state | Level | ASAF aspects | Source records | Checks and results |
|---|---|---|---|---|---|---|
| | | | | | | |

## Aspect coverage

For Customer, Supplier, Channel, Process, Structure, Information, Security,
Metrics, Systems, Technology, Management, Finance and Purpose, record the
relevant view or an explicit scope decision. Combine headings to fit your method.

## Decisions and readiness

- Principles and requirements:
- Options, costs and commitments:
- Accepted decisions, assumptions and unresolved questions:
- Release, operation, recovery and support responsibilities:
- Measures and proposed checks, with actual results kept separately:

## Change

Record Visioning, Transforming, Operating and Governing activities around
the design. Identify who may change it and which linked records must be reviewed.

## Object reference

| ID | Name | Meaning | Source and version | Views using it |
|---|---|---|---|---|
| | | | | |

Write ID (name) at first use in each page and diagram. Link back to this reference.