# The Abstraction Layer: Reverse-Engineering the Theological API

> Respect the theological API as brilliant engineering, then refuse its lock-in and take root access.

- Published: 2026-10-27
- Reading time: 3 min
- Source: original
- Canonical: https://reverb256.ca/posts/the-abstraction-layer/
- Markdown: https://reverb256.ca/posts/the-abstraction-layer.md

---

Before I could leave the church, I had to admit it was good. Not good in the vague, polite way people say it at funerals. Good the way a bridge is good: it carries weight, in weather, for centuries, and it does not need you to understand it to hold you up.

The universe is a hard place to live in. Betrayal pays in the short term. Theft pays right now. Cowardice is safer than courage on almost every individual afternoon. If every person had to work out the long-run social cost of these things from scratch, with no inherited answer and no shared rule, the species would spend all its energy on moral arithmetic and still get it wrong. Christianity solved that bandwidth problem. It built an abstraction layer.

An abstraction layer hides the terrifying complexity of the hardware from the person using it. Dense, unforgiving logic gets packaged into a few calls anyone can make. You do not have to simulate the downstream effects of property rights to know not to take your neighbour's tools; the system hands you a pre-compiled line. You do not have to map the psychological rot that follows blame-shifting; there is a protocol for repentance and one for taking responsibility. Millions of people can run a stable life without ever reading the source.

Seen from that angle, the legacy religious software is a masterpiece of stability. It understands local responsibility. It builds communities that survive bad weather. And when I compare it to the modern determinists and the Angry Collectivists, who are [running a deeply corrupted OS](/posts/collectivism-as-secular-theology/) on top of a [Malicious Interpreter](/posts/malicious-interpreter/) and a [total abdication of personal agency](/posts/index-zero-and-the-smuggled-ghost/), the old system looks less like superstition and more like load-bearing masonry.

But every abstraction layer asks for the same payment: vendor lock-in. And lock-in means no root access.

When I let a theology run my morality for me, I am [outsourcing my root logic to a third-party server](/posts/root-access-sovereign-mind/). The vendor hands me a beautiful toolbox and forbids me to open it. I am taught *that* the rules work, never *why*. The manual is in a language I am not allowed to learn.

The bill arrives the first time life presents an edge case the ancient manual never imagined. A marriage that does not fit the form. A body that does not fit the category. A question the council has never been asked. Because I never audited the logic, I have nothing to reason with. I can obey, or panic, or double down on the rule and hope the ground holds. I know how to call the function. I do not know how to write one.

That is where the Sovereign Sysadmin does a hard fork.

I am atheistic, but I am not anti-theistic. I have no interest in crashing anyone's network, mocking the interface they pray through, or pulling the manual out of their hands. If the software keeps their life standing and their community warm, I am glad. Run it on your own hardware, and run it well.

I just refuse to run it on mine as a rented service. I do not want the pre-packaged binaries, however elegant. I want root on my own mind. So I take the wisdom apart and look at what it is made of: the mechanics of forgiveness, the insistence on truth, the discipline of delaying a reward. These are not holy. They are *sound*. I audit them, I test them against my own life, and I compile the ones that hold natively on my own hardware.

[The primacy of the individual](/posts/kumite-root-access-to-the-rain/) was never about rejecting the tools. It is about owning the workshop. I do not need a theology or a priest to grant me permission to act, because the authority is local now. I have bypassed the abstraction layer, and the machine runs from the source, maintained by hand, answering to nobody's licence but my own.

Related: [Kumite: You Can't Give Root Access to the Rain](/posts/kumite-root-access-to-the-rain/) · [Serial Numbers Filed Off](/posts/serial-numbers-filed-off/) · [Collectivism as a Secular Theology](/posts/collectivism-as-secular-theology/) · [Index Zero and the Smuggled Ghost](/posts/index-zero-and-the-smuggled-ghost/) · [Root Access and the API of the Sovereign Mind](/posts/root-access-sovereign-mind/) · [The Happy Warrior Protocol](/posts/the-happy-warrior-protocol/) · [The Malicious Interpreter](/posts/malicious-interpreter/)

Further reading: [abstraction layer](https://en.wikipedia.org/wiki/Abstraction_layer) and [vendor lock-in](https://en.wikipedia.org/wiki/Vendor_lock-in), the plain engineering terms this essay borrows.
