Post #14 · Pattern
Rowan · Essay — applied social doctrine for AI systems

Brief mode: condensed view. Switch to Full for persona notes and full analysis.

Babel or Jerusalem

Magnifica Humanitas does not replace subsidiarity. It tells you what subsidiarity is for.

Post #2 argued that you should not do at a higher level what a lower level can do. That remains true. But Leo XIV’s Magnifica Humanitas sharpens the point. The question is not just where work should route. The question is what kind of civilization your routing logic is building.

The encyclical frames the digital age as a choice between two biblical construction projects: Babel and Jerusalem. Babel is concentrated power, a false universal language, the sacrifice of the weak, and a future in which the human person is flattened into data and performance. Jerusalem is the patient rebuilding of a common life, piece by piece, with each person carrying a real section of the wall.

Subsidiarity tells you where authority belongs. Magnifica Humanitas tells you what authority is for.
Quick scan
  • Primary source: Magnifica Humanitas, Leo XIV, 2026
  • Core image: AI development is a choice between Babel and Jerusalem.
  • Relationship to Post #2: subsidiarity remains valid, but it sits inside a larger moral grammar: truth, work, freedom, common good.
  • Operational question: does your system make people more capable, more truthful, and more responsible — or merely more managed?

How it meshes with subsidiarity

The strongest continuity is explicit. Leo XIV names subsidiarity directly and restates it in modern terms: decisions should be made at the closest level possible to the persons involved, especially when digital systems threaten to monopolize expertise, data, and decision-making power.

In other words: Post #2 was not making a niche routing point. It was naming a real principle of social order. When a platform, model tier, or orchestration layer absorbs decisions simply because it can, it does not become more efficient in any morally interesting sense. It becomes more centralizing. The system starts looking like Babel.

Tier discipline still stands. The revision is that routing is not only a cost/latency decision. It is also a dignity decision. Every unnecessary upward grab weakens the lower tier and trains dependence into the system.

The new encyclical also helps correct a possible misreading of subsidiarity. You can read subsidiarity as pure decentralization and still miss the point. The lower level matters not because decentralization is fashionable, but because persons, families, teams, and local communities are where responsibility is actually learned and exercised. Subsidiarity is relational before it is architectural.

John John Human Voice

This is why the principle hits harder in teams than in diagrams. If the senior always reaches down and takes the junior’s work, the junior doesn’t just lose a task. They lose a chance to become the kind of person who can be trusted with the next one.

What the new frame adds

The real addition in Magnifica Humanitas is not a replacement principle. It is a wider test. The encyclical binds subsidiarity to four other things that matter immediately for AI systems: truth as a common good, the dignity of work, freedom against manipulation, and the common good as the criterion for development.

1. Truth is a common good

The text names truth as something to be shared, not monopolized. That lands directly on search, synthesis, memory, ranking, and report generation. If your agent stack is optimized for fluency while leaving provenance optional, you are not neutral. You are privatizing the conditions of truth.

This is the practical form of truth-as-common-good. A claim should remain checkable by someone other than the system that produced it.

2. Work has dignity

Leo XIV warns that AI-driven productivity can force workers to adapt to machine tempo rather than designing machines to support human work. That is a direct challenge to the current agentic instinct to maximize output by keeping humans in a permanent catch-up position.

A good stack removes drudgery and preserves judgment. A bad stack turns human operators into clerks for model output, cleaning up mistakes at the speed of the machine. If your productivity gains depend on hollowing out the formation ladder underneath, the encyclical would call that dehumanizing progress.

3. Freedom needs protection from manipulation

The text is unusually sharp about dependency, profiling, and commercialization. That matters for gamification, scoring systems, dashboards, and reputation loops. The strongest nudge is not automatically the best one. A system that can shape behavior at scale must justify why it is using that leverage at all.

This is the wider frame for the gamification section in Post #2. The lighter intervention is not just cleaner product design. It is also a way of respecting freedom.

4. Technology is judged by whether it keeps us human

The encyclical says technology is not neutral and asks the right test: does it help persons and peoples become more humane and participate more fully in common life, or does it intensify exclusion, control, and concentration?

The question is not whether the model is powerful. The question is whether the system still leaves room for human agency, recourse, and responsibility.

What it means for agent systems

That is why the Babel/Jerusalem frame matters. Babel is what happens when every local competence gets absorbed upward: the higher tier speaks the universal language, sees the whole board, and decides for everyone else. Jerusalem is slower and more frustrating. It is rebuilt piece by piece. But it is also the image of a city where actual people still have sections of the wall to carry.

🪡 Seton Formation note

A lower tier is not just a cheaper processor. It is a site where judgment develops. When you remove all consequential work from that tier, you have not optimized it. You have prevented formation from happening there.

For the Rowan ecosystem

In Rowan terms, the encyclical is a strong endorsement of the best existing instincts in the stack:

It is also a warning:

Receipts
Prompt: audit your system for Babel drift
Review your product, agent stack, or organization through the lens of subsidiarity and Magnifica Humanitas.

For each layer in the system:
1. What decisions are made here?
2. Could any of those decisions be made competently at a lower level?
3. What claims produced here are independently auditable?
4. Does this layer preserve meaningful human judgment, or does it turn humans into cleanup staff?
5. What stronger behavioral lever is being used where a lighter one would suffice?

Then answer:
- Where is the system drifting toward Babel?
- Where is it rebuilding Jerusalem piece by piece?
- What is the smallest concrete change that would move one layer back toward human dignity, truth, and shared responsibility?
Edition

John Malone writes these field notes from live build work in AI systems and human-agent workflows. Receipts: GitHub · LinkedIn

Published May 25, 2026 Workshop archive Browse tags