Tech Talk · 7 essays
Data Architecture
Pipelines, layers, data quality and the models everything else stands on.
7 essays
- Green pipeline, wrong numbers: data quality at every layerA pipeline that ran is not a pipeline that is right. Part 2 of a series on data foundations for enterprise AI: the checks that run at every layer, the SLA on the gold layer, and who gets told when something breaks.
- Before you build the agent: working backwards to your data pipelineAn agent is only as trustworthy as the numbers under it. Part 1 of a series on data foundations for enterprise AI: getting every channel's data in, and modeling it so it agrees with itself.
- Data models agents can trustAnalysts fill gaps in a data model with tribal knowledge; AI agents fill them with confident guesses. Four ideas, with real Salesforce examples, for models an agent can answer from correctly.
- The semantic layer is the API for AIText-to-SQL demos well and fails quietly on finance data. Governed metrics, declared grain and semi-additive measures are what make an analytics agent trustworthy, and the semantic layer is how you hand them over.
- One customer, five systems: entity resolution and survivorship for finance dataCRM, contracts, ERP, billing and KYC each have their own idea of who the customer is. How I model a canonical party, match records without guessing, pick survivorship rules per attribute, and prove the result is right.
- As-of vs. as-was: bitemporal modeling for financial reportingLate prices, backdated deposits and restatements mean "what was the balance on December 31?" has two right answers. How to model both, and why auditors care which one you show.
- Ledger-first: a data architecture for a crypto custodianEvery finance number should be derivable from one immutable, double-entry ledger. How to model custody, balances and valuation so that dashboards are just views and reconciliation is a test.
No essays match your search. Try a broader term, or clear the search to see all essays.