What a Papal Encyclical Just Added to Your AI Governance Checklist

When Magnifica Humanitas dropped yesterday, I read it the way I imagine most Catholics read a new encyclical - as a member of the Church first, then as someone who has to ship AI systems on Monday. Those two readings landed differently. The theological one was expected. The operational one surprised me.

Pope Leo XIV released the document on May 25, 2026 - the 135th anniversary of Rerum Novarum, Leo XIII's 1891 encyclical on labor and capital during the industrial revolution. That date wasn't administrative coincidence. Leo XIV is making the same kind of intervention for the AI era that Leo XIII made for the factory era: not a technical blueprint, but a moral vocabulary for navigating a transformation that is already happening whether or not the Church has words for it.

I'm going to give you the operational read. But I want to be honest that I'm not writing this as a neutral analyst. I received this document as a Catholic. That context matters for why I think the vocabulary in it is worth taking seriously - not because the theology compels you, but because 1.4 billion people are now oriented around it.

This is a compliance artifact

Most AI ethics frameworks address outcomes: bias, harm, displacement, autonomous weapons. Magnifica Humanitas goes one level deeper. The encyclical's core claim is that the bigger risk isn't what AI does to outputs - it's what AI tempts users to believe about themselves. When "efficiency becomes the ultimate measure of value, human beings are tempted to see themselves as a project to be optimized rather than as persons called to relationship and communion" (MH 112).

That framing is harder to put in a JIRA ticket. But it's also harder to argue with - which is exactly why it will show up in board-level conversations before your quarterly review template does.

Within a quarter, expect this language in RFPs from Catholic-affiliated hospitals, in EU AI Act commentary, in bank ethics committee minutes. The institutions that move first on shared moral vocabulary set the terms of the conversation. The ones that don't will be retrofitting their answers.

Why framework-shaped beats policy-shaped

NIST gives you controls. The EU AI Act gives you obligations. Magnifica Humanitas gives you a vocabulary that survives translation across regulatory regimes. The encyclical explicitly avoids "technical policy blueprints" - and that's a feature. Portable moral frameworks outlast specific regulatory cycles. This one has institutional backing that no standards body can match.

The four questions (MH 237–240)

The operational core of the encyclical is four questions for evaluating AI-assisted technology. Here they are, with engineering translations:

Truth (MH 237): Does it help me remain faithful to the truth, despite the most appealing content? Retrieval grounding, citation surfacing, hallucination eval suites, refusal calibration. The clause "despite the most appealing content" is the real teeth - it's a direct indictment of engagement-optimized AI. If your system surfaces the most compelling answer rather than the most accurate one, you have a Truth problem in Leo's vocabulary.

Education (MH 238): Does it help educate me and allow me to educate others? Explainability surfaces, chain-of-thought logging, decision audit trails. The test I find most useful: if your AI product would be worse with a "show your reasoning" toggle, that's a signal worth sitting with.

Relationships (MH 239): Does it help me cultivate genuine closeness and cherish places where physical presence remains crucial? Human-in-the-loop gates, escalation paths, documented decisions about what not to automate. There are workflows - in healthcare, banking, HR - where automation is the wrong answer even when it's the cheaper one. The encyclical gives you a principled frame for defending that choice to a CFO.

Justice (MH 240): Does it help me participate in the promotion of justice and peace? Disparate-impact testing, demographic eval slices, red-team exercises for power-concentration use cases. The encyclical's language around "domination, exclusion, and death" will land in EU AI Act commentary within a year. Better to have the fairness audit cadence documented now.

The governance table

Most enterprise AI teams are already doing three of these four things. What's new is having a shared moral vocabulary to defend the work in front of a non-technical audience.

Encyclical question	Engineering control	Evidence to capture	Owner
Truth (MH 237)	Retrieval grounding, hallucination eval suite, refusal calibration	Factuality benchmark scores; % generations with verifiable citations; refusal rate on out-of-scope prompts	ML / Eval
Education (MH 238)	Explainability surface, chain-of-thought logging, decision audit trail	Audit log retention policy; user comprehension research; explain endpoint coverage	Product + Eng
Relationships (MH 239)	HITL gates on high-stakes actions, escalation to human, opt-out to non-AI path	Documented escalation thresholds; SLA for human handoff; map of intentionally non-automated workflows	Ops + Risk
Justice (MH 240)	Disparate-impact testing, demographic eval slices, refusal taxonomy	Fairness eval cadence; documented use-case exclusions; third-party bias audit	Trust & Safety + Legal

The harder question

The table is operationalizable. The anthropology underneath it is harder to test for.

MH 112 and 231 raise a question that doesn't fit in a row: does this product treat the user as someone to be served, or as a process to be perfected? It's the difference between an AI that makes a banker better at their job and an AI that replaces the banker with a measurement of the banker. I don't have a clean eval metric for that. But it's the question that will surface in board conversations first - and the teams that have thought it through will have better answers than the teams that haven't.

What to do this week

Three actions, scaled to where you sit:

If you run an AI product: Pre-draft the four-questions mapping for your top three features. You will be asked for this. Better to have a version ready than to write it under deadline.
If you sit on a governance committee: Get the encyclical's vocabulary into your review template before someone external - a regulator, a customer, an auditor - puts it there for you.
If you write RFP responses: Expect "human dignity," "openness and communion," and "domination, exclusion, and death" in customer questionnaires within a quarter. Have answers that are more than boilerplate.

The encyclical isn't going to change what good AI teams build. It's going to change what they have to say about what they build - and that's a real shift in the conversation.

The vocabulary just got a very large institutional endorsement. Worth being fluent before the next architecture review.