Data architect¶
A data-management role responsible for designing and governing the organization-wide structures, standards, flows, models, and platforms through which data is created, integrated, stored, secured, and used.
Core Idea¶
A data architect translates business and analytical needs into conceptual, logical, and physical data architectures and stewards principles for interoperability, lifecycle, metadata, quality, and technology alignment. The role inventories domains and flows, defines target models and standards, evaluates platforms and tradeoffs, and governs implementation so local systems contribute to a coherent data estate. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.
Scope of Application¶
Data architect belongs to data management and is useful where the analyst can specify the typed data management carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, then evaluate the role holds explicit responsibility for cross-system data structure and governance decisions and produces traceable architectural models, standards, transition plans, and review evidence. The scope is broad within that domain but bounded by the need for the role holds explicit responsibility for cross-system data structure and governance decisions and produces traceable architectural models, standards, transition plans, and review evidence. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.
Clarity¶
The abstraction clarifies a crowded vocabulary by making the role holds explicit responsibility for cross-system data structure and governance decisions and produces traceable architectural models, standards, transition plans, and review evidence the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name Data architect can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated.
Manages Complexity¶
Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Data architect. Data architect compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.
Abstract Reasoning¶
- Identify the carrier. State what the elements, states, objects, or observations are: the typed data management carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express the role holds explicit responsibility for cross-system data structure and governance decisions and produces traceable architectural models, standards, transition plans, and review evidence independently of one notation or implementation.
Knowledge Transfer¶
Knowledge transfers strongly among subfields of data management because they reuse the typed data management carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, The role inventories domains and flows, defines target models and standards, evaluates platforms and tradeoffs, and governs implementation so local systems contribute to a coherent data estate., and type the carrier, state every parameter and convention in the definition, test that the role holds explicit responsibility for cross-system data structure and governance decisions and produces traceable architectural models, standards, transition plans, and review evidence, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.
Relationships to Other Abstractions¶
Current abstraction Data architect Domain-specific
Parents (1) — more general patterns this builds on
-
Data architect is a kind of Role Prime
The proposed strict upward parent is
prime:role.
Neighborhood in Abstraction Space¶
Data architect sits in a crowded region of the domain-specific corpus (27th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.
Family — Knowledge Organization & Retrieval (39 abstractions)
Nearest neighbors
- Data sovereignty — 0.93
- Unidirectional data flow — 0.91
- Data store — 0.91
- Knowledge as a service — 0.91
- Data mart — 0.90
Computed from structural-signature embeddings · 2026-09-08