data architecture

Declared architectural convention

Record the adopted definition, modelling conventions and methods without treating one convention as universal.

1. Does this use of data architecture denote a discipline, an organisational arrangement or its description? definition
2. Which handbook, framework or institutional source supplies the adopted definition and methods? provenance

Allocation of architectural responsibility

Record which decisions belong to data architecture and which belong to adjacent practices under the named convention.

1. Which data decisions are architectural here, and which are delegated to governance, engineering or application teams? boundary
2. Which classification schemes, curricula or professional institutions explicitly recognise this field, and how do they place it? provenance

Concept boundaries and mappings

Record shared concepts and explicit mappings where domains use different meanings or levels of detail.

1. Which entities, events and measures must have agreed meanings across the architecture? definition
2. Where does an apparently shared term denote different concepts, populations or levels of aggregation? boundary

Identifier and schema continuity

Record how identifiers, relationships and temporal meanings survive representation changes.

1. How are identities reconciled across sources, including duplicate, merged or reassigned identifiers? definition
2. What mappings preserve relationships and historical meaning when logical or physical schemas change? action

Authoritative data and replicas

Record authority at an appropriate entity or attribute level and distinguish authoritative stores from derived copies.

1. Which source is authoritative for each critical entity or attribute, and under what conditions? definition
2. Why is each replica, cache or analytical copy needed, and who resolves conflicts between copies? boundary

Flow semantics and coupling

Record exchange contracts covering structure, freshness, ordering, duplication and compatibility where relevant.

1. For each critical flow, what delivery, ordering and duplicate-handling behaviour do consumers require? definition
2. How are contract changes introduced and incompatible consumers identified before release? action

Policy-to-control mapping

Record the provenance of handling requirements and the architectural points that enforce them.

1. Which accountable authority supplies classification, access and location requirements for each data domain? provenance
2. At which stores, interfaces and transformations are those requirements enforced and verified? action

Derivation and disposition

Record how retained, transformed and deleted data can be traced across operational and derived copies.

1. Which critical producer-to-consumer paths have verified lineage, and where does traceability stop? measurement
2. How do retention expiry, deletion and authorised preservation requirements propagate to replicas, extracts and backups? action

Quality thresholds and checkpoints

Record measurable quality requirements and where violations are detected or contained.

1. What completeness, validity, uniqueness and freshness thresholds apply to each critical use, with what denominators and observation windows? measurement
2. Where are invalid or late data rejected, quarantined, corrected or exposed with qualifications? action

Disruption and reconciliation

Record acceptable data loss, staleness and inconsistency alongside evidence that recovery arrangements meet them.

1. What data-loss window, recovery time and cross-store divergence are acceptable for each critical data service? measurement
2. How are replayed events, partial writes and conflicting replicas reconciled after interruption? action

Architecture-to-implementation trace

Record dated evidence for current-state claims, approved decisions and implementation deviations.

1. Which diagrams and decisions describe observed implementation, and which describe a proposed or approved target? boundary
2. What dated evidence supports conformance claims and identifies approved exceptions or unresolved deviations? provenance

Safe data transition

Record transition sequencing, reconciliation criteria and conditions for retiring old data paths.

1. Which producers, consumers, identifiers and historical records must migrate together or remain compatible during transition? boundary
2. What reconciliation, cutover and rollback evidence is required before authority transfers or an old store is retired? action

Check these first

Recalled without web access and unsourced; every item is a lead to verify.

1. Which of these check these first hold for the sense of data architecture this model covers, and on what evidence? provenance

Kinds and varieties

Recalled without web access and unsourced; every item is a lead to verify.

1. Which of these kinds and varieties hold for the sense of data architecture this model covers, and on what evidence? provenance

Standards and regulation

Recalled without web access and unsourced; every item is a lead to verify.

1. Which of these standards and regulation hold for the sense of data architecture this model covers, and on what evidence? provenance

Real-world use

Recalled without web access and unsourced; every item is a lead to verify.

1. Which of these real-world use hold for the sense of data architecture this model covers, and on what evidence? provenance

Failure modes and hazards

Recalled without web access and unsourced; every item is a lead to verify.

1. Which of these failure modes and hazards hold for the sense of data architecture this model covers, and on what evidence? provenance

Regional variation

Recalled without web access and unsourced; every item is a lead to verify.

1. Which of these regional variation hold for the sense of data architecture this model covers, and on what evidence? provenance

Neighbouring kinds and how to tell them apart

Recalled without web access and unsourced; every item is a lead to verify.

1. Which of these neighbouring kinds and how to tell them apart hold for the sense of data architecture this model covers, and on what evidence? provenance