Related Posts

Verifying claims across an AI engineering journey

14. Building AI Systems Honestly: The Gap Loop, What Works, and the Protocol That Emerged

TL;DR AI-generated code verification is the practical thread running through this 14-article capstone. It connects the platform’s architecture, security, compliance, data, model-risk, threat-modeling, and ISO governance work…

ISO 42001 Documentation: Controls, Owners and Evidence

13. ISO 42001 in Practice: Governing AI Systems When the Controls Outpace the Docs

TL;DR ISO 42001 documentation connects AI controls to their purpose, owner, evidence, and review. One self-assessment estimated how much of the technical-control and governance-documentation work was covered:…

Threat modeling AI systems with STRIDE, PASTA, and MITRE ATLAS

12. Threat Modeling AI Systems: STRIDE, PASTA, and MITRE ATLAS

TL;DR A threat model can document a control and still leave a practical question unanswered: what evidence shows that it works in the system? This article examines…

Fairness, Explainability, and Drift: The Last Mile of Production AI Governance

11. Fairness, Explainability, and Drift — The Last Mile of Production AI Governance

TL;DR Fairness checks compare outcomes across groups. A SHAP explanation estimates how inputs contribute to a score, while drift monitoring tracks changes in data. Using our banking…

Synthetic Data Governance for AI: Proving Data Provenance

9. Synthetic Data Governance for AI: Proving Data Provenance

TL;DR Synthetic data governance for AI comes down to one question: can you prove the data your model saw is the data your generator produced? The question…

8. Data Engineering for AI Agents: Pipelines, Real-Time Sync, and Vector Search

TL;DR Getting a data pipeline right is one job. Data engineering for AI agents is a different job. The agent has to actually consume that pipeline’s output,…

Leave a Reply