My 83-year-old dad said something to me today over the phone that I haven't been able to put down.
"Philosophy transcends science. Theology transcends philosophy. And when matters reach a high level of complexity, the three become intertwined", he said.
My first instinct was to argue. I've spent two decades in tech. I trust what science can settle. A claim that something sits above it sets off an alarm.
Then I asked him what he meant by "transcends." Authority, or depth?
He meant depth. And that changed everything.
Two readings of one word
"Transcends" can mean rules over — gets the final word, overrides the verdict below it. Most of the old fights between science and religion came from that reading. Treat depth as jurisdiction and you get conflict.
Or it can mean asks what the level below cannot ask of itself. The deeper discipline doesn't overrule the shallow one. It questions the ground the shallow one stands on without noticing.
On that second reading, his hierarchy is hard to argue with.
A stack of floors and ceilings
Each discipline takes as its starting floor what the one below treats as its ceiling.
Science's ceiling is an assumption: the universe is intelligible and regular. Science doesn't prove that. It can't. It needs it to start. That assumption is philosophy's floor — the thing philosophy interrogates.
Philosophy's ceiling is something like: there is a reason things are as they are, and meaning is possible. That's roughly where theology starts digging.
Depth, here, just means one thing. How far down toward the unquestioned ground are you willing to point your questions.
Keep asking "but why is that the case," and you eventually walk out of science. Keep going, and you walk out of philosophy. You end up somewhere that looks theological. Not because anyone seized authority. Because you ran out of floor.
Why complexity fuses them
The second half of his claim is the sharper one. At high complexity, the three intertwine.
I used to think that meant turf war. It doesn't.
It means the deep question becomes load-bearing for the shallow one. A cosmologist modeling a fine-tuned universe can't proceed without taking a position on what counts as an explanation. That's philosophy. And "it just is" as a stopping point — is that an answer or a surrender? That's the theological edge. The physicist didn't invite those questions. The complexity dragged them in.
You see it everywhere the problem gets hard enough. The foundations of mathematics. The hard problem of consciousness. The interpretation of quantum mechanics. At a certain depth, the boundaries stop respecting themselves. Not because the disciplines are sloppy. Because the questions don't care where we drew the lines.
Where I'd refine him
One pushback, offered in the spirit of thinking with him.
The stack may not be a single ladder. Depth might not run in one direction.
"What is consciousness" goes deep without obviously passing through "why is there something rather than nothing." Math's foundations go deep toward philosophy and barely graze theology. So his three tiers might be the dominant shaft of depth — not the only one.
That doesn't break the claim. It sharpens it. Theology sits at the bottom of one shaft: the contingency-of-existence one. The why-is-there-anything one. And that shaft happens to be where most other questions eventually drain. Which is why it feels like the bottom.
The real question isn't whether the stack exists. It's whether it's a single ladder or a watershed.
Why a product person cares
I didn't expect this conversation to land in my work. It did.
I've been learning and practicing agents: about how the defining trait isn't action, it's decision; about judgment becoming the scarce resource now that execution is cheap; about agency as a budget you spend on interpretation, planning, tool selection, recovery.
All of that is the same muscle my dad was describing. Depth of questioning. The willingness to keep asking what the level below is assumed and never checked.
A junior engineer ships the feature. A senior one asks whether the feature is the right floor to build on. The best people I work with go one level deeper than the problem hands them. They question the assumption underneath the requirement. That's the whole game now.
My dad wasn't talking about software. He was talking about inquiry itself. But the structure is identical. The value lies in how far down you're willing to point the question.
He's a doctor in his eighties. I run software products for a living. We ended up at the same place.
That's worth not putting down.