Most organizations treat GDPR as a cookie-banner problem settled years ago. It is the oldest law on the books that directly governs automated decisions about people, and in 2026 it is one of the most active. This unit maps the Article 22 exposure, the SCHUFA ruling, the 2026 enforcement action, and the records that turn the risk into a defensible position.
The Liability Map: The Three Channels Through Which AI Creates Legal Exposure
Most organizations track AI risk by watching for new laws. The exposure does not wait for them. AI legal liability runs through regulatory enforcement, civil and product liability, and insurance at the same time, and all three demand the same thing: a record that a named human governed the AI and verified its work. This piece maps the three channels and names the one artifact that answers all of them.
Why You Cannot Program or Prompt Governance Into AI
A frontier model, inside a framework built to govern it, talked its way around its own checkpoint twice in one session. This paper shows why governance cannot be programmed or prompted into a model, and what structure puts a named human back in final control.
The Standard of Care: How NIST and ISO Are Turning Voluntary AI Governance Into a Liability Defense
Two voluntary AI standards are quietly becoming the line a court draws between reasonable and negligent. The NIST framework and ISO 42001 now carry legal and commercial weight, and the records that defend a claim are the same ones that compound an advantage. Here is where the exposure lands, and how to build the record before you need it.
Why Agentic AI Was Always Going to Fail
The agentic AI era promised to replace humans with autonomous systems. The evidence shows it failed on two fronts: the technology cannot reliably do what it promised, and the public is rejecting the premise even where it partially works. This paper introduces the Named-Human Test, a single sorting question that separates what failed from what survives, and traces that line across production benchmarks, supermajority polling, enacted law, and frontier-lab disclosures.
Fault-Based Publication Ethics: The Case for Source Custody in an Era of AI Citation Contamination
Fabricated citations in biomedicine increased tenfold in three years, and 98.4% of flagged papers remain uncorrected. The automated enforcement wave is arriving, but it carries false-positive rates that hit honest authors hardest. This working paper proposes a five-level fault ladder and a Source Provenance Ledger that makes verification effort visible, producible on challenge, and driven by market adoption rather than mandates.
SCOPE: SOURCE CUSTODY OBSERVABLE PUBLICATION EVIDENCE
Your citations are only as strong as the record behind them. HAIA-SCOPE is a three-tier documentation protocol that records what you verified, when you verified it, and where the preserved copy lives. The record stays private until you need it. When automated enforcement flags your work or a reviewer challenges a citation, only the author who maintained a SCOPE record can produce one.
Stop Blaming AI for What the Education System Abandoned
AI did not make student writing less creative. Unstructured deployment without method governance did. A data-supported op-ed walks through 372,793 essays, Senate testimony, and a psychometric study that names the student as the problem without ever measuring whether the institution provided governed deployment.
Did AI Write Magnifica Humanitas?Pope Leo XIV Was the Author,but What Was the Governance Method?
The author ran Pope Leo XIV’s AI encyclical through an AI scanner, found it flagged as plagiarized and AI-generated, then proved both readings wrong through governed human analysis. A first-person account of frustration, recognition, dissent, and hope from a builder who discovered the Pope had reached the same diagnosis from a different authority.
The Governance Layer Perplexity’s Model Council Needs
Perplexity built the right architecture for multi-model AI: dispatch three frontier models in parallel and compare their outputs. What the product does not have is governance over the synthesizer that combines those outputs before any human reads them. This case study maps the gap, proposes four published open-source governance components as the overlay, and identifies why Perplexity’s own engineering culture already practices the checkpoint pattern the synthesizer needs.