How the LoCK Plugin Works

The first four articles have focused mainly on the Christian using artificial intelligence. Christians can use AI under the authority of Christ. Generative AI answers carry assumptions that need to be recognized, and the Christian remains responsible for discerning what those answers claim, what they assume, and what they ask a person to believe.

That responsibility cannot be handed back to the tool.

Now we can look more closely at the LoCK plugin itself. What actually makes the LoCK plugin different? Is it a different kind of artificial intelligence? Was it trained only on Christian material? Does it search the Bible before answering? Is it simply a general-purpose chatbot with instructions to include Bible verses?

None of those descriptions reaches the central difference. The LoCK plugin packages governance instructions and supporting references for an existing generative AI system. Those instructions guide how the AI is intended to approach and respond to a question.

Understanding that governance begins with a simple question: What governs the way the tool works through an answer?

Instructions Need Somewhere to Stand

Generative AI chatbots do not respond only to the words a user types into the prompt box. They can also operate under instructions that shape how they respond. Those instructions can direct a system to emphasize certain information, recognize particular concerns, acknowledge uncertainty, avoid certain kinds of responses, or approach a task in a more consistent way.

The LoCK plugin carries its governing instructions in a skill, a reusable set of instructions supported by reference documents. Installing the plugin makes that guidance available. To engage it deliberately in ChatGPT, select the installed plugin with an @ mention and give it the question or material you want to examine.

Once engaged, its instructions call for LoCK to continue governing subsequent answers until you explicitly ask to stop using LoCK. Changing the subject or asking for a shorter answer does not itself request that exit. This is intended behavior.

Instructions can make AI more useful, but they also push the problem one level deeper.

Telling an AI to be helpful does not settle what counts as helpful. Telling it to be fair does not define fairness. Telling it to consider several perspectives still leaves decisions about which perspectives should be considered and how they should be understood. Even telling an AI to provide a Christian answer leaves important questions unresolved. Christians themselves sometimes disagree about how Biblical teaching should be interpreted and applied.

Instructions do not eliminate interpretation. They need something to govern them.

This is the role of governance. Rather than providing a collection of preferred answers, governance establishes principles and priorities that shape how a tool approaches a question before it begins constructing a response.

The LoCK plugin does not attempt to list the Christian position on every possible issue. That would be impossible, and it would reduce Christian reasoning to searching for the correct response in a very large answer key. Instead, its governance establishes an order of authority. That order does not begin with LoCK.

Christian Reasoning Begins With Christ

It begins with Jesus Christ.

Jesus Christ was crucified and bodily raised from the dead. The resurrection is the foundational reality on which LoCK stands or falls. If Christ did not rise, the framework loses its foundation for beginning under His authority. But Christ was raised, and the risen Lord declared, “All authority has been given to me in heaven and on earth” (Matthew 28:18).

LoCK begins with Christ because Christian reasoning begins under Christ.

Christ is not simply the first item in an interpretive sequence. He is the center. His authority leads Christians first to His words and then to receive the rest of God’s Word under His authority. The New Testament bears witness to the risen Christ and explains and applies the significance of His life, death, resurrection, and reign. The Old Testament reveals the larger story of creation, fall, covenant, promise, judgment, and redemption that Christ affirmed and fulfilled.

That order is intentional. It is an interpretive guideline, not a ranking of inspiration. All of God’s Word is inspired and authoritative.

What Is LoCK?

From that foundation, Christians can look carefully at the world God has made. Creation can be studied. Evidence and observation can contribute genuine knowledge. History and culture can preserve wisdom and reveal important things about people and societies. Christian tradition can help us hear the wisdom and correction of believers who came before us. Competing worldviews can be understood carefully and may contain observations worth affirming.

These sources do not all perform the same role. Some sources govern interpretation. Others are brought before that authority for reflection and discernment.

A cultural belief does not receive the same authority as the teaching of Christ simply because both can be placed into an AI prompt. A scientific observation can tell Christians something true about God’s creation without becoming the authority that determines what human beings are for.

A competing worldview can be represented fairly and even expose weaknesses in our own reasoning without being granted authority over Christ or God’s Word.

Reflection can correct us. It can expose factual mistakes, weak reasoning, unfair representations, or assumptions we have mistaken for Biblical teaching. It cannot transfer governing authority away from Christ.

The order follows the authority.

Governance Shapes the Process, Not the Authority

This governing order shapes how the AI is instructed to approach a question when the LoCK plugin is engaged.

A general-purpose chatbot may approach a difficult worldview question by drawing from several perspectives, comparing them, and identifying areas of agreement or disagreement. As the earlier articles established, that can be useful.

The LoCK plugin begins somewhere different. It begins under the authority of Christ and God’s Word, seeks to understand the question from there, and then considers relevant evidence, observations, cultural claims, and competing perspectives.

It does not first gather perspectives and then locate Christianity among them. It begins with Christ and Biblical authority, then interprets the question and the relevant claims from there.

A programming question may require a programming answer. A historical question may require careful historical evidence. A question about biology may depend heavily on observation of the created world. Explicitly theological language does not need to be forced into an answer where it does not belong.

The governing foundation becomes more visible when interpretation enters the question. Human purpose, morality, identity, justice, relationships, truth, and competing religious claims cannot be settled merely by collecting information. The information still needs to be understood.

The LoCK plugin can consider ideas outside Christianity without simply rejecting them. Christians should be willing to hear competing claims accurately and recognize truth wherever it is found. Governance is not intended to shield the tool from those claims. It keeps clear what governs and what is being examined.

The LoCK plugin is designed to keep an explicit order of authority as the answer is formed, not merely to make every answer sound more Christian.

Governance can shape a process without guaranteeing the result.

The LoCK plugin can misunderstand a question. It can provide inaccurate information. It can reason poorly, misapply a Bible passage, or fail to follow its own governing instructions consistently. The governance itself was written by fallible human beings and may need correction or refinement.

Nothing about the framework changes artificial intelligence into something spiritually authoritative. God’s Word remains authoritative. The LoCK plugin does not.

The responsibility described in the previous article remains with the Christian. We still need to examine an answer, read Biblical passages in context, verify important factual claims, and challenge weak reasoning.

Explore the LoCK Plugin

The LoCK plugin attempts something more limited. Its governing commitments are made explicit and intentionally ordered beneath an authority outside the tool itself. When it works as intended, that governance can support Christian discernment without asking the Christian to reconstruct the same foundation with every prompt.

Governance does not give the LoCK plugin Christ’s authority. It attempts to keep the tool operating beneath an authority it does not possess.

The LoCK plugin must therefore remain open to correction.

A Framework That Can Be Questioned

Explaining how the LoCK plugin works does not prove that its approach is correct. Making its assumptions and governance explicit makes them easier to examine.

Some objections are immediate. If the LoCK plugin begins with Christ, is its reasoning circular? Does explicit Christian governance force the AI toward predetermined answers? Who determines how God’s Word should be interpreted? Could a tool designed around Christian commitments become an echo chamber? If the governance itself was written by fallible people, why should anyone trust it?

LoCK does not need protection from those questions.

A framework that asks Christians to examine the assumptions beneath AI answers should allow its own assumptions to be examined. It should also be clear about where authority resides, what the framework can and cannot do, and where its reasoning may fail.

Some criticism may expose errors in implementation. If the LoCK plugin misuses a Bible passage, represents another worldview unfairly, or repeatedly produces weak reasoning, pointing to its governance does not solve the problem. The answer should be corrected, and if necessary, the governance should be corrected as well.

Other criticism reaches the foundation itself. It asks whether Christ should stand at the center in the first place.

LoCK cannot finally answer that question by appealing to itself. LoCK is a human framework. The LoCK plugin applies it to an AI tool. Neither possesses the authority on which the framework depends.

The deepest claim stands outside both:

Jesus Christ was crucified, bodily raised from the dead, and reigns as Lord.

If that is not true, LoCK loses its foundation. If it is true, Christ’s authority does not depend upon whether LoCK explains Him correctly. Faithfulness to Christ matters more than faithfulness to LoCK.

The final article will put these criticisms directly to the framework rather than asking the framework to protect itself from them.

Previous
Previous

How Should Christians Discern AI Answers?

Next
Next

Common Criticisms of the LoCK Plugin