Blog

Deep dives into data governance, AI, architecture, and engineering.

Data Architecture & Engineering June 19, 2026 · 35 min read

Knowledge Graph Cost Modeling: Build vs Buy, Layer-by-Layer Budgets, And Team Composition

Appendix B of the Knowledge Graph Practitioner's Guide. Decomposes the trilogy cost-and-benefit roll-up from Part 11c into the dollar lines a CFO can defend. Covers per-layer cost decomposition (foundation, operational, governance, agent), license-versus-infrastructure-versus-headcount splits, the build-versus-buy decision per layer, the 24-month team curve from one ontologist to a 12-person multi-discipline platform, the role-by-role compensation reality (ontologist, knowledge engineer, graph platform engineer, entity resolution engineer, governance lead, AI engineer), what ROI looks like at steady state, six failure modes in KG cost modeling, an eight-question budget diagnostic, and a tiered Do Next table for the CFO, the CDO, and the procurement officer.

#knowledge-graph#cost-modeling#build-vs-buy#team-composition
Data Governance & Management June 19, 2026 · 34 min read

Knowledge Graphs for Data Governance: Lineage, CDEs, and Master Data as a Graph

Most enterprise Data Governance has plateaued at a catalog plus a lineage tool plus a glossary plus a policy register, and four disconnected stores cannot answer the questions a regulator now asks. This article shows how a knowledge graph turns Data Lineage, Critical Data Elements, master data, and policy into one queryable substrate, with the OpenLineage-to-PROV-O bridge from Part 7 as the connective tissue. Worked patterns for BCBS 239, ECB RDARR attribute-level lineage, GDPR Article 30, and EU AI Act Article 10. Part 10 of the Knowledge Graph Practitioner's Guide.

#knowledge-graph#data-governance#data-lineage#critical-data-elements
Data Architecture & Engineering June 19, 2026 · 23 min read

Identity, Reference, and Inference: How a Graph Becomes Knowledge

Identity is the load-bearing decision in a knowledge graph. IRIs are identifiers, not URLs. owl:sameAs is not as simple as it looks. Entity resolution is not optional. Inference is what turns stored facts into knowledge, and the choice between forward chaining (materialization) and backward chaining (query rewriting) is the second-most expensive design call after identity. This article gives the working design rules for all three and the W3C reasoning profiles (OWL 2 EL, QL, RL) that production KGs actually pick. Part 5 of the Knowledge Graph Practitioner's Guide.

#knowledge-graph#entity-resolution#owl#inference
Data Governance & Management June 19, 2026 · 30 min read

Operating a Knowledge Graph: Change, Versioning, and Evolution at Scale

A knowledge graph that cannot answer 'what did the graph say on the day the auditor pulled the report' is not in production. This article gives the operational architecture of a KG: bitemporal modeling, named-graph versioning, ontology release management with semantic versioning and OWL deprecation markers, SHACL-based backward compatibility verification, contract-based change management at the consumer boundary, and the migration playbook for ontology refactors. It covers what every change must preserve, how to evolve without breaking downstream agents, and the seven failure modes that turn a healthy graph into shelfware in eighteen months. Part 8 of the Knowledge Graph Practitioner's Guide.

#knowledge-graph#data-governance#ontology-management#versioning
Industry Teardowns June 19, 2026 · 11 min read

What Writing Sixteen Articles on Knowledge Graphs Taught Me (and What I Got Wrong)

The conclusion to the Knowledge Graph Practitioner's Guide. An honest accounting from the translation layer: what surprised me writing the series, the three things I think the series got wrong, three gaps it never covered, and a whole-series Do Next table tiered by reader readiness. Part 12 of the Knowledge Graph Practitioner's Guide.

#knowledge-graph#data-architecture#data-governance#ontology
Data Architecture & Engineering June 19, 2026 · 36 min read

The Knowledge Graph Tool and Technology Landscape: An Honest Vendor Map for 2026

Appendix A of the Knowledge Graph Practitioner's Guide. The first place in the series vendor names appear in earnest. Maps the seven layers of a production KG stack (triple stores, property graph stores, hybrid stores, virtualization, entity resolution, LLM extraction, governance metadata) onto the 2026 vendor landscape, names Lakeside Trust Bank's pick at each layer with rationale, gives a triple-vs-property-vs-hybrid decision tree, walks through what changed between 2025 and 2026 (the Ontotext-SWC merger, the SAP-Reltio acquisition, AWS Neptune Analytics' GenAI track, Stardog Voicebox, Senzing v4, the Microsoft GraphRAG cost reckoning, the rise of LightRAG and Graphiti), enumerates six vendor-selection failure modes, and closes with an eight-question vendor diagnostic and a tiered Do Next table.

#knowledge-graph#vendor-landscape#triple-store#property-graph
Data Architecture & Engineering June 19, 2026 · 24 min read

Sourcing the Graph: Building Knowledge from Structured and Unstructured Data

Most enterprise data is split between structured systems with stable schemas and unstructured documents with no schema at all. A knowledge graph has to ingest both. This article gives the working design for the two construction tracks: deterministic mapping for relational and tabular sources (R2RML, Direct Mapping, RML, virtualization vs materialization), and probabilistic extraction for unstructured text (end-to-end relation extraction, LLM-assisted graph indexing, incremental construction, schema-first vs schema-emergent). It covers where the two tracks meet, the failure modes specific to construction, and the decision tree for picking a sourcing strategy. Part 6 of the Knowledge Graph Practitioner's Guide.

#knowledge-graph#r2rml#rml#llm-extraction
Data Governance & Management June 19, 2026 · 31 min read

Quality, Provenance, and Trust: Why Knowledge Graphs Fail Audits

A knowledge graph that cannot answer 'where did this fact come from?' is a liability, not an asset. This article gives the working design for the trust layer of a KG: the four quality dimensions (consistency, completeness, currency, correctness), the SHACL validation gate, the four provenance models (per-triple reification, named-graph, RDF-star, PROV-O), and the regulatory cross-walk to BCBS 239, GDPR Article 30, and the EU AI Act. It covers what every triple must record, how trust differs from quality, and the seven failure modes that show up in audits. Part 7 of the Knowledge Graph Practitioner's Guide.

#knowledge-graph#data-governance#provenance#shacl
AI Governance & Safety June 19, 2026 · 34 min read

Knowledge Graphs for AI Agents: The Retrieval Architecture That Makes Context Real

Vector RAG returns relevant chunks but loses the connections between them. Long context degrades the moment it grows. Agents that have to reason across multiple entities, several hops, and time eventually hit a ceiling that more tokens cannot raise. This article gives the retrieval architecture that breaks that ceiling: GraphRAG and its production variants (Microsoft GraphRAG, LightRAG, LazyGraphRAG, HippoRAG 2), the four-layer agent memory model from CoALA mapped to a knowledge graph backbone, the comparative landscape of agent-memory frameworks (Letta, Mem0, Zep/Graphiti), and the trust-tier-aware retrieval pattern that prevents an agent from confidently citing bronze content as if it were gold. Part 9 of the Knowledge Graph Practitioner's Guide.

#knowledge-graph#ai-agents#graphrag#agent-memory
AI Governance & Safety June 19, 2026 · 39 min read

Building a Production Knowledge Graph at Lakeside Trust Bank: The Relationship-Banker Agent

Part 11c of the Knowledge Graph Practitioner's Guide. Closes the Lakeside Trust Bank trilogy. The same graph from Parts 11a and 11b now backs the relationship-banker agent. Covers how the CoALA four-layer memory model maps to Lakeside's named graphs, how three production workflows (portfolio decisions, client-meeting prep, advisor-facing summaries) map to three trust-tier policies (strict-tier-floor, tier-segregated, tier-explicit-citation), how the agent and the EU AI Act conformance assessor read the same substrate, what Lakeside got wrong on the way, the contract discipline that keeps the agent operable across quarterly FIBO releases, a cost-and-benefit roll-up that previews Appendix B, and a Do Next table that spans foundation, operational, governance, and agent layers.

#knowledge-graph#reference-architecture#financial-services#ai-agents
Industry Teardowns June 19, 2026 · 21 min read

LinkedIn's Economic Graph Teardown: A Knowledge Graph You've Used Today

A teardown of LinkedIn's Economic Graph as a knowledge graph: 1.2 billion members, 69 million companies, 41 thousand skills, all stitched together by typed relationships and machine-inferred connections. The first article in The Knowledge Graph Practitioner's Guide. We use a system you already know to introduce the foundational vocabulary you will need for the rest of the series.

#knowledge-graph#linkedin#economic-graph#ontology
Data Architecture & Engineering June 19, 2026 · 31 min read

Building a Production Knowledge Graph at Lakeside Trust Bank: Foundation and the Operational Layer

The capstone of the Knowledge Graph Practitioner's Guide. A mid-size US bank takes the foundations from Parts 3 to 8 and turns them into a working production graph. This first piece covers the Monday-morning question that no spreadsheet-and-five-systems architecture can answer in time, the deliberate-versus-accidental KG choice, the modular FIBO-anchored ontology Lakeside imports, the 8-stage pipeline that flows Track 1 (R2RML on the warehouse) and Track 2 (LLM-extracted credit memos) into one graph, and the operational use case (customer 360, beneficial ownership, real-time transaction risk). Part 11a of the Knowledge Graph Practitioner's Guide.

#knowledge-graph#reference-architecture#financial-services#beneficial-ownership
Data Architecture & Engineering June 19, 2026 · 30 min read

Building a Production Knowledge Graph at Lakeside Trust Bank: The Governance Layer

Part 11b of the Knowledge Graph Practitioner's Guide. The same Lakeside Trust Bank graph from Part 11a takes a Tuesday-morning examiner question, then collapses BCBS 239 attribute-level lineage, ECB RDARR Data Lineage expectations, GDPR Article 30 ROPA, and EU AI Act Article 10 training-data provenance into four SPARQL templates against one graph. Covers the OpenLineage to PROV-O bridge through Lakeside's Spark and dbt pipelines, the 280 CDEs as typed nodes with 5,600 hasImplementation edges (Counterparty Credit Exposure as the worked example), the trust-tier-by-reporting-surface table specialized to Lakeside, and the named-graph version chain across a quarterly FIBO release.

#knowledge-graph#reference-architecture#financial-services#data-governance
Data Architecture & Engineering June 19, 2026 · 24 min read

Ontology, Taxonomy, Schema: The Vocabulary That Makes Knowledge Possible

Three words that get used interchangeably in architecture meetings and mean three different things in production. Taxonomy is classification. Schema is shape. Ontology is meaning plus rules. This article gives the precise distinction, the RDFS/OWL/SHACL stack, three worked examples (Schema.org, FIBO, SNOMED CT), and the design patterns that decide whether your ontology survives year two. Part 4 of the Knowledge Graph Practitioner's Guide.

#knowledge-graph#ontology#taxonomy#schema
AI Products & Strategy June 19, 2026 · 26 min read

The Politics of Knowledge Graphs: Pushback, Sponsorship, And The 'Just Use A Database' Argument

Appendix C of the Knowledge Graph Practitioner's Guide. The political map. Covers the five most common KG objections (just use a database, the property graph alone is enough, we already have a catalog, this is a science project, just point GPT at it) and the rebuttals each one earns; the five-sponsor map across CDO, CTO, CFO, General Counsel, and CIO with their questions, artifacts, and failure modes; the four-or-five-store anti-pattern from Part 10 specialized to the political problem (each store has an organizational owner with budget authority); the leadership-transition risk anchored to the 2.5-year CDO tenure data; the small-wins-then-trust-then-scope-expansion pattern for political ramp; six failure modes in KG politics; an eight-question political diagnostic; and a tiered Do Next table.

#knowledge-graph#organizational-politics#executive-sponsorship#data-governance
Data Architecture & Engineering June 19, 2026 · 19 min read

What a Knowledge Graph Actually Is (and Is Not): From Tables to Triples to Meaning

Knowledge graphs sit at a junction of three different conversations: graph data models, ontologies, and identity. This article gives the precise definition, the two dominant paradigms (RDF and property graphs) compared honestly, and the four things a knowledge graph is not (graph database, knowledge base, semantic layer, vector store with relationships). Part 3 of the Knowledge Graph Practitioner's Guide.

#knowledge-graph#rdf#property-graph#ontology
AI Products & Strategy April 19, 2026 · 17 min read

Gemma 4, Decoded: Why Google Released It Free and How It Actually Works

Google released Gemma 4 under Apache 2.0 on April 2, 2026. The license change is the real story, not the benchmarks. This is the three-tier framework for 'open' AI (closed, open-weight, open-source), a technical breakdown of how Gemma 4's MoE and multimodal pipeline work, and a practitioner decision flow for picking the right tier.

#gemma-4#open-weight#open-source#ai-strategy
AI Governance & Safety April 11, 2026 · 12 min read

Privacy-Preserving Computation: Encrypted Processing, Federated Learning, and the Explainability Paradox

Part 6 showed Meridian rejecting federated learning (single-tenant architecture) and deferring homomorphic encryption (47x latency). This article explains the mechanics behind those decisions, introduces secure multi-party computation, and reveals the tension between GDPR's explainability mandate and privacy protection. Concludes with a capstone PET decision framework spanning Parts 7 through 9.

#data-governance#data-privacy#data-protection#privacy-engineering
AI Governance & Safety April 11, 2026 · 9 min read

Privacy-Enhancing Technologies: Masking, Tokenization, and De-identification

Part 3 introduced PETs as governance decisions. Part 6 showed Meridian evaluating them. This article explains how each technique actually works: static and dynamic masking, vault-based and format-preserving tokenization, and the k-anonymity family of de-identification methods.

#data-governance#data-privacy#data-protection#privacy-engineering
AI Products & Strategy April 4, 2026 · 7 min read

Willison's Agentic Engineering Patterns: What Data Practitioners Should Steal

Bad code crashes visibly. Bad data looks plausible. That asymmetry makes agent-assisted data work riskier than software, and it is why Simon Willison's Agentic Engineering Patterns guide matters for data practitioners. His Red/Green TDD maps to data contracts before transformation. His testing discipline gives teams a framework for agent verification. But some patterns need adaptation: 'pipelines are cheap' is only half true, and hoarding knowledge is harder when institutional context lives in people's heads, not in code.

#agentic-engineering#coding-agents#data-quality#judgment-in-the-loop
AI Governance & Safety April 4, 2026 · 14 min read

Context Engineering, Formalized: Five Criteria That Validate the Agent Quality Thesis

Vishnyakova's 'Context Engineering' paper (arXiv 2603.09619) proposes five production-grade quality criteria for agent context and a four-level maturity pyramid. The framework independently validates the thesis from our three-part agent quality series and extends it with Isolation, Economy, and two higher-order disciplines: Intent Engineering and Specification Engineering.

#context-engineering#ai-agents#data-quality#ai-governance
AI Products & Strategy April 4, 2026 · 8 min read

Multi-Agent Systems: When One Agent Isn't Enough

Nine articles in this series used a single agent. This one explains when that stops being sufficient and what to do about it. Four signals tell you it is time. Three patterns handle 90% of cases. The hardest part is not building the system; it is debugging it when something goes wrong.

#ai-agents#multi-agent-systems#agent-orchestration#agent-architecture
AI Governance & Safety April 4, 2026 · 23 min read

Privacy in Practice: Diagnosing the Gaps and Building the Foundation

A fictitious B2B SaaS company receives a DPIA request it cannot answer. This walkthrough applies the privacy framework from Part 3 to build Data Classification, retention schedules, consent architecture, and sub-processor transparency from scratch.

#data-privacy#data-governance#privacy-engineering#ai-governance
AI Governance & Safety April 4, 2026 · 17 min read

Privacy in Practice: From Compliant to Operationally Ready

Meridian Analytics completes its privacy transformation. This walkthrough covers cross-border transfer documentation, EU AI Act compliance mapping, PET assessments, the governance operating model, and what the company looks like six months later when Allianz asks the same DPIA questions.

#data-privacy#data-governance#privacy-engineering#ai-governance
AI Governance & Safety April 4, 2026 · 7 min read

The Data Privacy Practitioner's Guide

A ten-part series from teardown to framework to implementation. Two company analyses (Netflix, Apple), an 8-component privacy program framework, the 2026 regulatory landscape, a complete implementation walkthrough using a fictitious B2B SaaS company, a three-part deep dive into Privacy-Enhancing Technologies, and a synthesis of what it all means for practitioners.

#data-privacy#data-governance#gdpr#ai-governance
AI Governance & Safety April 4, 2026 · 8 min read

What This Series Taught Me About Privacy

The conclusion to the Data Privacy series. Two company teardowns, a framework, a regulatory map, two implementation walkthroughs, and a three-part deep dive into Privacy-Enhancing Technologies. Here is what surprised me, what I got wrong, and what practitioners should do next.

#data-privacy#data-governance#gdpr#ai-governance
AI Products & Strategy April 1, 2026 · 12 min read

Observability: Seeing What Your Agent Actually Does

Your monitoring says 200 OK. The agent returned the wrong answer. Traditional APM was designed for deterministic software. Agents reason, branch, and call tools in sequences they decide at runtime. This article covers the five dimensions of agent observability, the tooling landscape, and a practical instrumentation plan.

#ai-agents#agent-observability#monitoring#data-observability
AI Products & Strategy April 1, 2026 · 14 min read

Prompt Engineering for Production Agents

Production agents need prompts that produce consistent, structured output under adversarial conditions. This article covers the five patterns that separate production prompt engineering from tutorial-grade prompting: explicit criteria, few-shot examples, nullable fields, enum-with-fallback, and output format contracts.

#ai-agents#prompt-engineering#structured-output#tool-calling
AI Products & Strategy March 25, 2026 · 18 min read

Build a Real Agent This Weekend: From Zero to a Working Research Assistant

The series has defined agents, established design principles, and mapped failure modes. This article builds one. A complete research assistant agent with three tools, structured error handling with error categories and retry logic, context management, and a basic eval, all in one runnable Python file using the Anthropic SDK.

#ai-agents#agent-development#tool-calling#anthropic-sdk
AI Governance & Safety March 25, 2026 · 16 min read

Context Is the Program: Why Data Quality Inside the Agent Matters More Than the Model

Pike's Rule 5 says data dominates. In AI agents, the context window IS the data structure. This article traces why context quality determines agent behavior more than model capability, maps the five criteria that define good context, and shows what happens when stale data enters the reasoning loop unchecked.

#ai-agents#context-engineering#data-quality#ai-governance
AI Governance & Safety March 25, 2026 · 15 min read

Guardrails and Safety: The Boundaries Every Agent Needs

Pike's Rule 4 says fancy algorithms are buggier. In agent systems, complexity multiplies failure surfaces. This article maps the three guardrail layers every agent needs, identifies the gap most frameworks miss, covers escalation patterns and workflow gates, and explains why simpler architectures are safer.

#ai-agents#ai-governance#agent-safety#guardrails
AI Products & Strategy March 25, 2026 · 8 min read

Pike's Five Rules Are Now the Five Rules of Agent Development

Rob Pike wrote five rules of programming in 1989 at Bell Labs. Thirty-seven years later, they map onto AI agent development with striking precision: measure before tuning, start simple, and get the data right. Nobody has made this connection explicitly. Here is the mapping, the evidence, and the framework it gives you.

#ai-agents#agent-development#context-engineering#agentic-engineering
AI Products & Strategy March 25, 2026 · 15 min read

The Self-Improving Agent: From Static Prompts to Learning Systems

Most AI agents run the same prompt every time. The best ones evolve. This article maps the spectrum from static to self-improving agents, introduces the inner loop / outer loop architecture, and walks through a real system that learns from feedback weekly. Pike's Rules 3-4 set the boundary: start simple, add complexity only when measurement demands it.

#ai-agents#self-improving-agents#agentic-engineering#learning-systems
AI Products & Strategy March 25, 2026 · 17 min read

From Problem to Agent: An Implementation Reference Guide

The series taught ten concepts across ten articles. This capstone walks through all of them applied to one problem: building a Data Quality monitoring agent. Seven steps, from problem definition through production deployment, showing the decision-making process that separates agent projects that ship from agent projects that stall.

#ai-agents#data-quality#implementation-guide#context-engineering
AI Products & Strategy March 25, 2026 · 11 min read

What Is an AI Agent (and What Isn't)?

An AI agent is a system that uses an LLM to decide which actions to take in a loop until a goal is met. This article breaks down the four components every agent shares, the spectrum from chatbot to autonomous agent, what tool calling actually looks like in code, and the design principles that separate good tool definitions from bad ones.

#ai-agents#agent-architecture#tool-calling#ai-fundamentals
Data Governance & Management March 18, 2026 · 24 min read

The Data Privacy Regulatory Landscape in 2026: GDPR, CCPA, AI Laws, and the Insurance Market for When AI Goes Wrong

A practitioner's reference to the global privacy regulatory landscape. GDPR fines have crossed EUR 5.6 billion. Twenty US states have privacy laws with no federal standard. The EU AI Act is phasing in. And a new insurance market is emerging for AI agents that go off script. This is where the rules stand, what they require, and what is coming next.

#data-privacy#data-governance#gdpr#ccpa
Data Governance & Management March 17, 2026 · 20 min read

How to Build a Privacy Program in the Age of AI

A practitioner's framework for building a privacy program that treats AI data as a first-class concern. Covers Data Classification for training data, retention schedules for ML pipelines, consent architecture, third-party transparency, cross-border transfers, EU AI Act Article 10, NIST AI RMF, privacy-enhancing technologies, and governance operating models.

#data-privacy#data-governance#ai-governance#eu-ai-act
Data Governance & Management March 16, 2026 · 15 min read

Apple Privacy Teardown: When Privacy Is the Product, Where Does It Break Down?

A Data Governance teardown of Apple's privacy practices. What Apple actually collects, how hardware margins fund privacy positioning, where Apple falls short on Siri, China, and its own ad network, and what practitioners can learn from privacy as a business strategy.

#data-privacy#data-governance#apple#app-tracking-transparency