Scripture · Christian traditions · Historical context

Theoria

Read Christian sources alongside the world that shaped them, and explore the enduring questions they raise.

The world behind the words

To understand a work, understand its world.

Every work belongs to a world. Geopolitical power, technology, and social life shape what its author sees and assumes. The Chronicle places writings alongside that environment, helping us understand their meaning in context instead of projecting our own world onto them.

Christian Chronicle Explore a period. Follow a source.

Open the full timeline

Zoom through history and select a record to inspect its context. Continue in the full Chronicle.

What I built

A study desk that preserves who is speaking.

Theoria brings Scripture, original-language tools, Christian history, and theological sources into a cited research workspace. It supports conversation, comparison across traditions, and longer investigations that can be saved and revisited.

The public app offers Catholic, Orthodox, and Reformed readings. The portfolio opens a Catholic inquiry; each conversation keeps its chosen perspective, while material from another tradition is identified as comparison. Catholic sources include Trent, Vatican I, the Baltimore Catechism, Scripture, and the Fathers.

  • Sources keep their roles. Scripture, confessional standards, historical witnesses, and commentary remain distinguishable in retrieval and answers.
  • Questions can outgrow a chat. Persistent conversations, inspectable citations, and the Christian Chronicle support sustained study.
  • Meaning leads back to the text. Logos MCP searches passages and underlying themes, then returns references the reader can inspect.

Why it matters to my work

Timeless problems. Changing technology.

My theory is that systems and problem themes are timeless. We keep confronting the same questions: who can act, whose account can be trusted, how a community shares responsibility, and how to recognize a convincing mistake.

Technology moves under us. Its new vocabulary can make us believe we have entirely new problems. A larger model, a faster database, or another layer of automation changes our capabilities; the questions of authority, interpretation, incentives, and judgment remain.

Biblical stories give those tensions human form. I use them to examine architectural decisions: where a boundary belongs, what must remain shared, and how a system should respond when confidence outruns evidence.

These are connections I draw in retrospect. I use the passage to sharpen an engineering question, then judge the design by what it actually does.

An echo of Ecclesiastes 1:9–11

Three connections

Three decisions, read beside Scripture.

I used Logos MCP to explore decisions from Theoria, the Enterprise Intelligence Platform, and Oracle, then read the passages in context. These three connections each turn an engineering problem into a question about authority, responsibility, or judgment.

01 / Theoria

The altar that almost started a war.

Joshua 22:10–34 ↗

Preserve a source’s purpose as carefully as its content.

The problem. A research system can quote a source accurately and still misrepresent it by assigning it the wrong authority. Similar wording is especially dangerous when Scripture, commentary, and different confessions share a search space.

The decision. I bound each Theoria conversation to a reading profile and preserved source roles through retrieval. A comparative text or historical witness must remain identifiable when it enters an answer.

The connection. In Joshua 22, the western tribes see an altar and prepare for war, reading it as a rival place of sacrifice. The builders explain that it is a witness of shared belonging. The decisive discovery is what the object is for. That is the same question a source-aware system must preserve before it turns retrieved words into a claim.

Read the passage & examine the parallel

“not for burnt offering, nor for sacrifice; but it is a witness between us and you.”

Joshua 22:28 · World English Bible

The dispute concerns Israel’s covenant worship. The passage does not resolve modern denominational differences; the architectural parallel is the discipline of establishing a source’s role before interpreting it.

The engineering question: Could the same wording be retrieved from two different source classes without the answer silently treating them as the same authority?

Read the full chapter

02 / Enterprise Intelligence Platform

Moses could not be the whole system.

Exodus 18:13–26 ↗

Scale responsibility together with the rules that govern it.

The problem. As one application becomes a platform for many agent products, every new capability raises the same question: who is allowed to do what? Delegating work without a shared standard can spread inconsistent decisions across the organization.

The decision. I made tool contracts and runtime authorization part of the common platform. A call carries the user’s context; capability, sensitivity, and row scope are checked before execution. New products inherit those controls.

The connection. Jethro finds Moses judging from morning to evening and warns that both he and the people will wear out. His counsel combines common statutes, qualified delegates, and a route for difficult cases. The striking detail is that he distributes judgment while preserving its governing standard. The parallel is bounded authority, with clear limits on what each part of the system may decide.

Read the passage & examine the parallel

“They brought the hard cases to Moses, but every small matter they judged themselves.”

Exodus 18:26 · World English Bible

The passage concerns morally accountable people judging under divine law. It is not a specification for software services. I draw from its relationship between shared standards, delegated responsibility, and escalation.

The engineering question: Can a new agent product use the common controls, and will a request outside its granted authority stop before it reaches the data?

Read the full chapter

03 / Oracle

Four hundred forecasts. One unwelcome answer.

1 Kings 22:5–28 ↗

The system proposing an answer should not control its acceptance test.

The problem. An automated research system can produce persuasive hypotheses faster than it can establish whether they hold up. Agreement among agents can repeat the same assumption; an impressive backtest can benefit from information that would not have been available at the time.

The decision. Oracle separates discovery from quantitative acceptance. Its validation design uses chronological holdouts and gaps between training and test windows. The research agent proposes a candidate; separate checks determine whether its evidence holds up.

The connection. Ahab’s prophets promise success. Before Micaiah enters, a messenger asks him to match their favorable answer. He refuses to make that agreement his standard. The architectural connection is not simply “listen to a dissenter.” It is to protect a check whose answer cannot be chosen by the people who want the proposal to succeed.

Read the passage & examine the parallel

“Please let your word be like the word of one of them, and speak good.”

1 Kings 22:13 · World English Bible

Micaiah’s authority in the narrative is God’s word. An engineering check remains a fallible measurement. The useful connection is the freedom to contradict a desired outcome; disagreement alone cannot establish truth.

The engineering question: If every research agent agrees, can an unchanged acceptance test still reject the candidate?

Read the full chapter

Inside Theoria

A reading has an identity. Every source has a role.

The architecture keeps the chosen tradition, the evidence returned, and the conversation’s history connected throughout the work.

  1. 01 / Perspective

    Choose a reading

    A new inquiry binds to a tradition’s profile and retrieval service. Its perspective remains explicit throughout the conversation.

  2. 02 / Retrieval

    Ask the source tools

    Logos MCP retrieves passages, doctrine, original-language detail, comparisons, and relevant themes with source references.

  3. 03 / Evidence

    Preserve the distinctions

    An ancient witness, a commentary, and a confessional standard can contribute differently without becoming interchangeable authority.

  4. 04 / Conversation

    Keep the work

    Cited answers stream into persistent threads. The server owns completion so the work can continue beyond a browser connection.

Explore the product

Bring a question worth following.

Research beta

Read a passage, compare Christian traditions, trace a question through history, or investigate a recurring problem in your own work. Theoria keeps the sources available for inspection.

Open Theoria ↗

Arthur's portfolio assistant

Beyond the resume.

Get to know the experience behind the resume.

    Ask about my experience, the systems I've built, or how I lead delivery.

    Public experience · Saved in this browser