# BP-V04 (Information relationships)

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: Records and retained history.
- Design state: PROC-01 (Process-only proposal)
- Level: Logical
- Design: Proposed; checks unrun
- Scope: Case meaning shared with the later software option
- ASAF aspects: Information, Process
- View page: /blueprint/information
- Editable source: information.mmd
- Export: information.svg

## Reading the view

A cancelled booking may have historical cancellation cases, with at most one active case. Each active case has one current owner assignment. Agreement and confirmation histories retain corrections. A resolved case requires confirmation matching its current agreement.

## Key

- Crow’s-foot ends show how many records may be related. The text states which record is current.
- History may contain several assignments and agreements; only one of each can be current.

## Linked records

- [I1 (Cancellation case record)](/blueprint/objects#i1)
- [ID-DEF1 (Learner agreement definition)](/blueprint/objects#id-def1)
- [ID-D1 (Shared case register)](/blueprint/objects#id-d1)
- [ID-V1 (Case meaning checks)](/blueprint/objects#id-v1)

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