The blueprint connects the same service rule across purpose, people, information, systems and operation: R1 (Continuous ownership) preserves learner agreement and continuous ownership through every handover.
Record set
BP-R01 (Blueprint record set) contains the complete example, eight diagrams and the reference catalogue. The reusable outline can be adapted to your own method.
| Record | Completed example | Blank outline |
|---|---|---|
| Complete blueprint | Markdown | Blueprint outline |
| Cover and index | Completed cover | Use the outline above. |
| View descriptions | Individual records below | Blank view |
| Object reference | Web page · JSON · CSV | Adapt the object table in the outline. |
| Source records | Reference table | Retain a source and version for each reference. |
| Reading conventions | Notation key | Adapt the key with the views. |
Trace a requirement
Follow O1 (Accepted resolution) through P1 (Learner agreement), R1 and OP-D1 (Accepted-transfer procedure) to SI-C01 (Transfer acceptance contract). Then inspect SI-V1 (Interface checks) and TD-R1 (Recovery procedure). The object reference links each record to its explanation. These checks are proposed; the fictional service has no measured results.
Diagram files
| View | Editable source | Static export | View record |
|---|---|---|---|
| BP-V01 (Service overview) | Mermaid | SVG | Description |
| BP-V02 (Accepted handover) | Mermaid | SVG | Description |
| BP-V03 (Work and responsibility) | Mermaid | SVG | Description |
| BP-V04 (Information relationships) | Mermaid | SVG | Description |
| BP-V05 (Case lifecycle) | Mermaid | SVG | Description |
| BP-V06 (Systems and rules) | Mermaid | SVG | Description |
| BP-V07 (Access and authority) | Mermaid | SVG | Description |
| BP-V08 (Runtime and recovery) | Mermaid | SVG | Description |
The manifest identifies the source files, renderer and exports by their hashes. The website displays the same SVG files offered here. Keep the edition note with copies and adaptations.
Methodology configuration
Start with the question each view must answer. Combine its fields with your architecture document, model catalogue or decision log. Retain enough identity and source information to follow a change between views.
Dials
Choose the scope and detail needed for the next decision, then the review cadence and decision authority. See Methodology configuration.
Return to the blueprint.
The Portal-authored blueprint downloads use CC BY 4.0. Credit Adrian Sutherland and Architecture Portal, link to the licence and source edition, and identify changes. See the edition note.