Method

This project reads Scripture, history, institutions, symbols, and contemporary culture through a Christian theological lens. It is not detached religious studies, and it should not pretend to be more certain than its evidence allows.

The aim is discernment and repentance: to see how holy gifts can become idols, how false embodiment takes shape, and how Christ calls the whole person and the whole body back into truth.

This page gathers the public method for reading, receiving, testing, and publishing material in the public library.

Governing Distinctions

Raw material is preserved carefully, but preservation is not publication. Publication is not canonization. Canonical development is not automatic authority.

Every document should keep these layers distinct: source, public reading copy, theological argument, canonical proposal, devotional image, and editorial tool. A preserved document has not automatically become a public teaching. A public essay has not automatically become a settled theological verdict. A useful tool has not become an authority.

The archive must remain a servant of faithful keeping, not a monument to its own growth.

Institutions And Form

The Architecture of Apostasy is not anti-institutional by default.

Christianity is embodied and communal. It requires real practices, real authority, real memory, real discipline, real worship, real care for the poor, real teaching, and real forms of common life.

The question is not whether form exists. The question is what spirit the form serves.

Institutions can corrupt holy gifts, but institutions can also preserve, distribute, and protect them. A church, school, household, ministry, order, archive, or public project becomes dangerous when it preserves its own form as if that form were the living God. But the answer is not structureless purity. Faithful form makes love durable when it remains repentant, accountable to Christ, and attentive to the vulnerable.

Claim Types

The archive uses several kinds of claims. Readers should be able to tell which kind is being made.

Doctrine

Doctrine names claims the project receives as Christian confession: Christ is Lord, the Logos became flesh, sin deforms the person, repentance is necessary, and redemption is found in Christ.

Doctrinal claims should be grounded in Scripture and accountable to the historic Christian faith.

Exegesis

Exegesis asks what a biblical passage says in its literary, canonical, and theological context.

When the project reads Numbers 21, 2 Kings 18, Romans 3, Romans 11, or Revelation 2-3, it should distinguish the text itself from the later pattern the text helps illuminate.

Typology And Analogy

Typology and analogy are the project’s main tools for reading patterns across time.

The Nehushtan pattern is not a claim that every church, institution, or historical moment repeats Israel in a mechanically identical way. It is an interpretive proposal: holy gifts can become idols when detached from repentance, humility, and living communion with God.

Analogies can clarify, but they can also flatten history. They should be handled as invitations to discernment rather than shortcuts around evidence.

Historical Judgment

Historical claims require sourcing, proportion, and humility.

When the project names Constantine, the Great Schism, the Reformation, modern missionary movements, church-growth models, or Western consumer religion, it should not treat complex histories as if they were settled by a single theological sentence.

The public essays are currently uneven in visible sourcing. The goal is to keep improving them with notes, bibliographies, rival readings, and clearer distinctions between evidence, interpretation, and warning.

Prophetic Warning

Prophetic warning names the project’s strongest register. It is the language of diagnosis, repentance, pruning, and return.

That register can be necessary. It can also become careless if it turns every pattern into an absolute verdict. The project should speak urgently without confusing urgency with omniscience.

Publication Method

New material enters through a deliberate process before it becomes public, canonical, or held in reserve.

Source received
  ->
Preserve faithfully
  ->
Classify the claim and genre
  ->
Identify source needs and rival readings
  ->
Review for theological fit, pastoral risk, and Christological resolution
  ->
Publish, revise, canonize, or hold in reserve

Material is not published merely because it exists. It should be read, classified, tested, and placed where it can serve the path of return without confusing raw intensity with public teaching.

If a file cannot be placed safely, it should be held with a clear explanation. Ambiguity is not failure; it is a signal that human editorial judgment is needed.

Intake Questions

Before a document moves forward, it should answer these questions:

  1. What kind of document is this?
  2. What created good is being examined?
  3. What was entrusted, and to whom?
  4. What legitimate authority, responsibility, or capacity is present?
  5. What corruption, false logos, or fallen liturgy is being exposed?
  6. Where does keeping become possession?
  7. Who begins paying the cost of preserving the keeper, office, institution, or symbolic order?
  8. What cry is being heard?
  9. What wound does this document carry?
  10. What claim types are present?
  11. What evidence is needed?
  12. What rival reading should be considered?
  13. Where does it belong in the repository?
  14. Does it clarify the path of return, or merely enlarge the library?
  15. Does it resolve in Christ, or only diagnose collapse?
  16. What would repentance, restored keeping, or faithful release look like?
  17. If this is an essay with a companion image, has the image been placed near the top of the public Markdown copy and listed in the gallery?

These questions slow the project down when speed would confuse raw intensity with faithful increase.

Publication Standards

Public work should have a clear purpose, belong in the right public context, identify its claim type or genre, and avoid confusing raw material with canonical theological development.

It should clarify the path rather than merely expand the site. It should preserve humility where evidence is incomplete, resist contempt, and gesture toward Christ, restoration, repentance, or faithful keeping.

Canonical work carries a higher burden. It should use canonical terms consistently, distinguish doctrine from synthesis, cite sources proportionate to its claims, include objections or cautions, and resolve in Christ.

After review, a document may be published, revised, used to improve an orientation page, paired with a fitting image, held for sourcing or pastoral review, preserved privately, or declined.

Holding a document back is not failure. Sometimes faithful keeping means refusing to turn every source, wound, warning, or image into public material.

Keeper-Oriented Questions

Pages about authority, guardianship, institutions, leadership, family, office, protection, judgment, force, or The Keeping of the Troth should ask the keeper’s questions explicitly.

What has been entrusted? What gives the keeper authority to act? What limits that authority? What capacities make the keeper dangerous? How can the keeper receive correction? How does the keeper distinguish threat from disagreement? What signs show that keeping has become possession? What conditions terminate the keeping? What does faithful release look like? What does it mean here to say, “I am not the Shepherd”?

Validation

Mechanical checks serve editorial judgment. They catch drift, missing links, stale references, and publication gaps, but they do not decide theological truth.

Warnings should be handled according to their type. Some warnings call for immediate fixes before publication. Others identify real editorial work that should not be rushed mechanically.

Human review remains responsible for doctrine, tone, evidence, pastoral risk, and whether a piece should be public at all.

Anti-Nehushtan Rule

Tools, symbols, documents, AI systems, and institutions must remain signs and servants. They may help preserve memory, order labor, clarify claims, test consistency, and guide readers, but they must never become sources of ultimate authority.

When any project artifact begins to receive the trust, fear, obedience, or finality that belongs to Christ, it has become Nehushtan. The right response is not contempt for the artifact, but repentance: return the sign to its proper service and the heart to the living God.

Revelation And Modern Application

Readings of Philadelphia, Laodicea, or other biblical images applied to modern church history should be treated as typological warnings unless an essay explicitly provides historical argument for a stronger claim.

That means such readings ask, “What does this biblical warning expose in us?” before they claim, “This period of history definitively maps onto that church.”

Rival Readings

Readers from Catholic, Orthodox, Protestant, Anabaptist, Pentecostal, secular historical, or other traditions may contest parts of the interpretation. Those objections matter.

The project is stronger when it faces rival readings rather than treating disagreement as blindness. A general map of major objections and alternative interpretations is gathered in Rival Readings.

Source Development

The archive preserves drafts, source material, and working notes, but public-facing essays need visible citations proportionate to their claims.

Source development is ongoing. The goal is not to make every warning academic in tone, but to make each public claim more testable, accountable, and fair to serious rival readings.

How To Read The Project

Read the essays as theological arguments with a prophetic edge. They are meant to provoke repentance and discernment. They are not final scholarly monographs.

The right response is neither passive agreement nor easy dismissal. The better response is testing:

  1. What kind of claim is being made?
  2. What evidence supports it?
  3. What rival reading should be considered?
  4. What would repentance or faithful embodiment look like here?