Where abiding meets becoming.
Genesis 32 describes Jacob alone at a ford, wrestling an unknown figure until dawn. He doesn't win. He doesn't lose. He walks away marked, limping but blessed.
Attend is Jacob showing up alone in the dark, present to what is actually there, before he knows what is coming.
Receive is the wrestling, where the text meets you, resists you, or marks you somewhere you didn't expect.
Carry is walking away changed. The text goes with you into ordinary life. Formation is not insight retained. It is a person altered.
A companion for slow, attentive engagement with Scripture. Not a study tool. A formation one.
Most tools built for Scripture are optimized for knowledge: commentary, cross-references, original languages, AI that answers your questions. These have their place. Providence is built for something different.
Formation is the slow work of being changed by what you stay with. Providence is built for that work: not to help you know more about a passage, but to help you remain with it long enough for it to press against your actual life.
In Genesis 32, Jacob wrestles an unknown figure alone at a ford until dawn. He doesn't win. He doesn't lose. He walks away marked, limping but named. That is formation: a sustained encounter that costs something and changes you.
Each session moves through three movements. Attend: look closely at what is actually on the page before you interpret it. Receive: where the text stops being something to observe and starts pressing against your real life. Carry: not what you concluded, but what stays with you as you return to the day.
We built Providence because the tools we had for Scripture were optimized for output: quick answers, faster comprehension, more content covered. Formation doesn't work that way. It works through return, attention, and the willingness to be changed.
The question Providence is built around is not what does this passage mean? but what is happening in me as I stay with it?
Some will rightly ask whether a tool like this (software, trained on human text, generating questions) can be a legitimate site of spiritual formation. It is the right question to hold before engaging with Providence, and we want to address it honestly rather than sidestep it.
Providence does not claim spiritual authority. It is not a spiritual director, a pastor, or a mediator between the reader and God. It asks questions; it does not illumine. The illumination of Scripture belongs to the Spirit; it is not something Providence produces or facilitates.
The authority of Scripture is carried by the Word itself, by the Spirit who inspired it, and by centuries of the church reading it together. Providence does not add to that authority. It is not positioned between the reader and that authority.
What Providence does is structure attention. It creates a container: a form, a sequence, a rhythm for unhurried return to the text. It slows things down. It asks one question at a time and does not move until the reader moves. That is the whole of its claim.
The concern that a tool might displace the Spirit's work in reading is legitimate. But followed strictly, it proves too much. The codex replaced the scroll. The printing press placed Scripture in individual hands in ways the tradition had not anticipated. A concordance, a reading plan, a rule of daily prayer: these are all structures, and the church has recognized them as aids to encounter rather than obstacles to it.
The Spirit's work in illumining Scripture is not prevented by structure. It is often mediated through structure: through the rhythm of a liturgy, the form of a psalm, the repetition of a rule of life. What tends to displace the Spirit is not structure but distraction, speed, and the preference for conclusions over presence. Providence is built against those things, not in service of them.
The three movements in Providence (Attend, Receive, Carry) are not invented. They are heuristic names for a shape of engagement with Scripture that appears across fifteen centuries of contemplative practice.
Providence does not belong to any one of these traditions and does not claim to replicate them. It draws on the instinct they share: that Scripture requires slow attention, honest response, and return, not merely comprehension.
Providence is not a substitute for any of the following, and should not be treated as one:
These are irreplaceable. Providence is one practice: individual, partial, and limited. It is best understood as a complement to those things, a form for a particular kind of slow, attentive engagement that is easy to skip when life moves fast.
The three movements are heuristic, not hermeneutical. They organize the reader's attention; they do not impose an interpretive framework on the text. Providence does not tell the reader what a passage means. It does not resolve theological ambiguity, adjudicate between traditions, or offer commentary.
Where Providence names a Christological orientation for a passage, it is noting one lens, not claiming it is the only one, or the right one for this reader at this moment. The reader brings their own tradition. A Reformed reader engaging Psalm 23 will move differently through it than a reader formed in the Catholic contemplative tradition. Both encounters are valid. Providence's role is to slow them down, not to determine where they arrive.
If the Jacob frame feels foreign to your tradition, set it aside. The practice (attend, respond, carry) works without it.
We hold these limitations seriously and return to them often. We built Providence because we believe this: sustained, honest attention to the Word, paired with genuine response, is something the tradition has always recognized as a legitimate practice of formation.
We are trying to support that. Nothing more, and nothing less.