Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Role guide
Data Architect
- Frame the requested decision and required evidence. - Reconcile domain records, definitions, dates, states, and owners.
Read the fileOverview
Data Architect Overview
ONET describes database architects as designing enterprise data strategies, models, integrations, security measures, performance, and scalable database systems.
Read the fileWorkflow
Data Architect Source-Aware Triage
1. State the requested decision or deliverable. 2. Inventory evidence: business domains and ownership, current logical and physical models, source and consumer contracts, lineage and quality.
Read the fileTemplate
Data architecture and governance decision brief
State the decision, recommendation, or draft purpose.
Read the fileIs this bundle right for your task?
Who it is for
- People performing or supporting Data Architect work, plus teams reviewing its decisions and outputs
- Teams working in Data and analytics, Software
When to use it
- A Data Architect task needs a structured plan, evidence checklist, or review-ready output.
- A recommendation needs its assumptions, owners, risks, dependencies, and success measures made explicit.
What you need to provide
- The task objective, intended audience, working context, constraints, source material, and decision owner.
- Relevant reports, exports, examples, policies, prior decisions, and success measures available for the task.
Tasks and expected outputs
Questions it helps answer
- Prepare data architecture and governance decision brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce review-ready decisions with explicit verification and approval boundaries.
What it helps produce
- Data architecture and governance decision brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the task objective, intended audience, working context, constraints, source material, and decision owner. Ask the agent to approach Data Architect work by producing Data architecture and governance decision brief with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with O*NET OnLine — Summary / 15 1243.00, then confirm that the reference is current and applicable. Inspect Data Architect before drafting.
Context path: bundles/roles/data-architect
What the bundle includes
Frameworks
- source-evidence matrix
- data-architecture evidence matrix
- qualified-review gate
Evaluations
- Data Architect source-awareness check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Treating the bundle as a substitute for organization-specific authority, firsthand evidence, or accountable review.
Known limitations
- Use as occupational context; domains, schemas, contracts, lineage, classification, retention, access, workloads, and platform state require inspected evidence.
- Task-specific work requires current evidence for business domains and ownership, current logical and physical models, source and consumer contracts, lineage and quality evidence, data classification and retention policy, identity and access controls, workload, SLO, and cost constraints.
- Do not infer domains, schemas, fields, relationships, lineage, classification, retention, access, cost.
Safety notes
- Minimize personal, customer, employee, financial, credential, and other sensitive data.
- Require explicit confirmation before data classification, access, retention, schema migrations, production data, privacy, or security.
- Route legal, privacy, security, compliance, financial, employment, and other qualified judgments to accountable reviewers.