Explainability is the property of an AI system (or of a layer added to it) that lets you see why it gave a specific answer: which inputs mattered, which rules fired, and what would have changed the outcome.
No jargon, no math
A large model is a black box: billions of tuned weights turn your input into an output, with no dials to read. Explainability is the toolkit for shining a light inside, or around, that box. There are two families. Interpretable-by-design systems are simple enough to read directly: a scorecard, a decision tree, a rules engine; you see the whole path. Post-hoc explanations work on black-box models: feature attribution (SHAP-style scores) ranks which inputs pushed the answer up or down; counterfactuals tell you what small change would have flipped it (“two fewer late deliveries and this supplier would have passed”). Neither is a confession straight from the model: post-hoc scores are faithful approximations, useful for auditing and debugging, not proof of the true reason. That is the boundary: an explanation can be plausible and still be a reconstruction. High-stakes use needs explanation plus audit plus human review, especially where the EU AI Act demands it.
Interpretability is the degree to which you can look inside an AI model and understand what its internal parts represent and how they combine to produce an answer, as opposed to explainability, which constructs a plausible justification after the decision is made.
ReadAn AI audit is a structured review of how an organisation actually uses AI: every tool, model and workflow is inventoried, then tested for accuracy, data exposure, cost and compliance, with findings ranked by risk and a remediation plan attached.
ReadModel evaluation is the process of measuring how well a model performs on data it has never seen, using metrics and test sets agreed in advance, before you trust it with real decisions.
Read§ 03
We design and ship AI systems with permissions, logs and human approval. It starts with a 30-minute scoping call.