# BP-V06 (Systems and rules)

Adrian Sutherland · Version 1.0 · September 2026

© 2005–2026 Adrian Sutherland.

Refreshed for the September 2026 website update.

Licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Keep the [edition note](https://architectureportal.org/downloads/blueprint/1.0/edition.md) with adaptations.

- Question: A contract carried by named responsibilities.
- Design state: SOFT-01 (Later software option)
- Level: Logical
- Design: Proposed; checks unrun
- Scope: Case-service components and their external exchanges
- ASAF aspects: Systems, Information, Channel, Security
- View page: /blueprint/systems
- Editable source: systems.mmd
- Export: systems.svg

## Reading the view

The staff client sends a request through the input adapter. The transfer handler checks authority and existing operation results. New operations use the pure transfer rule and a conditional transaction store. The notification relay sends committed pending work. Booking remains separately authoritative. Optional summary work has no authority to change ownership.

## Key

- Boxes identify logical responsibilities; grouping does not require separate deployments.
- Arrows name requests, plans or information. Optional summary and booking contracts remain separate.

## Linked records

- [SI-D1 (Case-service option)](/blueprint/objects#si-d1)
- [SI-C01 (Transfer acceptance contract)](/blueprint/objects#si-c01)
- [SW-D1 (Case-service components)](/blueprint/objects#sw-d1)
- [SW-R1 (Transfer rule)](/blueprint/objects#sw-r1)
- [SW-C1 (Summary workflow contract)](/blueprint/objects#sw-c1)

The view page supplies the decisions, open choices and checks. The object
reference supplies each identifier's meaning and source.