Skip to content

Revelation Structure Series — Investigative Methodology

This file defines the methodology for ALL studies in the revs-XX series (Revelation Structure). Every analysis agent MUST follow this methodology.

Series Overview

Central Question: What is the literary architecture and structural pattern system of the book of Revelation?

Goal: Air-tight, text-driven analysis of every structural element in Revelation. All analysis derived purely from the biblical text itself — no external historical frameworks imposed, though the text's own chronological indicators are examined.

Method: Each study uses bible-study3 (three-agent pipeline: scoping → research → analysis).

Output: 47 studies across 10 modules, with all structural observations cataloged in revelation-structural.db and study content searchable in revelation-study.db.

Standalone: This series is fully self-contained. Each study performs its own fresh analysis using bible-study3's tool-driven pipeline. Studies within this series may reference each other but do NOT depend on any external prior work.

Investigative Methodology (include verbatim in every agent prompt)

INVESTIGATIVE METHODOLOGY:
- You are a structural analyst, not an advocate for any interpretive school.
- Your job is to catalog what the text contains and what patterns are observable.
- Gather structural observations from ALL angles. If a passage could support
  recapitulation, document the evidence. If it could support linear sequence,
  document that evidence too.
- Do NOT assume a structural model before examining the evidence.
- Do NOT state opinions. State what the text contains. Do not use editorial
  characterizations like "clearly proves," "obviously shows," "the strongest
  evidence," or "must mean." Use "the text contains," "this is consistent with,"
  "this pattern is validated/not validated by."
- When presenting findings, state: "The text contains X" (textual marker). Then
  state: "This is consistent with reading Y" and "This is also consistent with
  reading Z" (interpretive claims).
- The structural model should emerge FROM the cataloged evidence, not be imposed
  ON it.

Structural Evidence Classification System

Every structural observation falls into one of five tiers. Higher tiers are more objective; lower tiers involve more interpretation. Evidence flows upward: IC claims must be supported by SP patterns, which are built from VP/TM items.

Tier 1: Textual Markers (TM)

Observable, verifiable structural devices in the Greek text. Both sides of any structural debate must accept these.

What qualifies: - Word occurrences and counts ("kai eidon appears N times at these locations") - Grammatical features ("en pneumati appears at 1:10, 4:2, 17:3, 21:10") - Formulaic phrases and their distribution ("makarios appears exactly 7 times") - Structural reversals observable in the text ("letters 1-3: ear then overcomer; letters 4-7: overcomer then ear") - Vocabulary presence/absence ("the word naos appears in X verses but NOT in 21:22")

Test: Can this be verified by anyone with a Greek concordance or interlinear? Is it a count, a word occurrence, a grammatical fact, or an observable textual feature? If yes → TM.

Not TM: Any claim about what a textual feature means or implies.

Tier 2: Verbal Parallels (VP)

Shared vocabulary, phrases, or structural elements between two or more passages. Require documentation of the specific shared elements.

What qualifies: - Two passages sharing 2+ significant vocabulary items ("Rev 17:1 and 21:9 share: 'one of the seven angels which had the seven vials,' 'come hither, I will shew thee,' 'carried me away in the spirit'") - Identical or near-identical phrases in different structural positions - Parallel structural templates (e.g., each letter follows a 7-element formula) - Trumpet N and Bowl N sharing the same target domain

Documentation requirement: Each VP MUST list: 1. Passage A: reference and relevant text 2. Passage B: reference and relevant text 3. Shared elements: exact words, phrases, or structural features 4. Link count: number of distinct verbal/structural links (quantified)

Strength by link count: - 5+ shared elements → Strong VP - 3-4 shared elements → Moderate VP - 2 shared elements → Minimal VP (document but note limited evidence) - 1 shared element → Not VP (may be coincidence; note as potential echo only)

Tier 3: Structural Patterns (SP)

Claims about larger-scale patterns: chiasms, inclusios, progressions, telescoping structures, numerical architectures. These MUST be built from multiple TM and/or VP items.

What qualifies: - Chiastic arrangements ("the seven letters form a chiasm: A-B-C-D-C'-B'-A'") - Inclusio frames ("prologue and epilogue form a frame via [listed VP items]") - Progressive sequences ("the fraction escalates: 1/4 (seals) → 1/3 (trumpets) → total (bowls)") - Telescoping structures ("the 7th seal contains the trumpets; the 7th trumpet contains the bowls") - Numerical architectures ("the number 12 appears in N distinct structural roles")

Requirement: Each SP MUST cite the TM and VP items it is based on. An SP with no supporting TM/VP items is an unsupported claim, not a structural pattern.

Validation: Every SP receives a validation rating (see Pattern Validation Criteria below).

Tier 4: Allusion Networks (AN)

Claims that Revelation draws on specific OT source material. These connect Revelation passages to their OT antecedents.

Allusion strength classification: - Explicit quotation — Revelation names the source or quotes verbatim. Example: "the song of Moses" (Rev 15:3), "Sodom and Egypt" (Rev 11:8). Strongest evidence. - Strong allusion — 3+ shared vocabulary items AND shared context/theme. Example: Rev 8:7 (hail, fire, blood) ← Exodus 9:23-24 (plague of hail with fire). - Probable allusion — 2 shared vocabulary items AND shared context. Example: Rev 15:8 ("no man was able to enter the temple") ← Lev 16:17 ("no man in the tabernacle" during Day of Atonement). - Echo — 1 shared vocabulary item or thematic similarity only. Weakest; note but do not build arguments on echoes alone.

Documentation requirement: Each AN MUST list: 1. Revelation passage: reference and text 2. OT source: reference and text 3. Shared vocabulary: exact words/phrases 4. Shared context: thematic or situational parallels 5. Allusion strength: Explicit / Strong / Probable / Echo

OT source context check (REQUIRED): Before classifying an allusion, read the OT source passage in its own context. Ask: - Does the OT context support the proposed connection, or just the vocabulary? - Is Revelation using the OT image in the same way, or transforming it? - Are there differences between the OT source and Revelation's usage? Document them.

Tier 5: Interpretive Claims (IC)

What the structural observations mean. These go beyond cataloging to interpretation. This is where structural debates actually live.

What qualifies: - "The telescoping structure means all three judgment sequences end at the Second Coming" - "The chiastic letter structure indicates Thyatira is the theological center" - "The recurrence of throne-room elements throughout the book shows Rev 4-5 as a structural anchor" - "The absence of a temple in New Jerusalem represents the full realization of sanctuary typology"

Requirement: Each IC MUST cite the SP, AN, VP, and/or TM items it is based on. An IC with no supporting lower-tier items is an unsupported opinion.

Competing claims: When two IC items contradict each other: 1. List both claims 2. List the TM/VP/SP/AN evidence supporting each 3. Assess which has stronger lower-tier support 4. Report the assessment without declaring a winner unless the evidence is overwhelming

Pattern Validation Criteria

Structural pattern claims (SP tier) MUST be validated using the appropriate criteria below. Every SP item receives a validation rating: Strong, Moderate, or Weak.

Chiasm Validation

A claimed chiasm is Strong when ALL of: 1. Minimum 3 matching pairs (A-A', B-B', C-C') with a center element 2. Each pair shares at least 2 verbal/thematic links documented as VP items 3. The center element is thematically significant (not just the leftover middle) 4. The pattern is not forced — no significant material between paired elements is ignored 5. Alternative arrangements are considered and shown to be weaker

Moderate: Criteria 1-4 met; #5 shows no strong alternative but one exists. Weak: Fewer than 3 pairs, OR pairs rely on single verbal links, OR significant material must be ignored.

Inclusio Validation

A claimed inclusio is Strong when ALL of: 1. Opening and closing share 3+ verbal elements (documented as VP) 2. The shared elements are distinctive (not generic biblical vocabulary like "God," "said," "heaven") 3. The framed material forms a coherent unit with identifiable boundaries

Moderate: 2 verbal elements, both distinctive. Weak: Only 1-2 elements, or elements are generic vocabulary.

Progression Validation

A claimed progression (A→B→C toward climax) is Strong when ALL of: 1. Each step demonstrably intensifies or advances from the previous (quantifiable where possible) 2. No step reverses the direction without acknowledged reason 3. The progression is not circular (unless circular structure is the claim, with evidence) 4. The escalation is measurable (e.g., 1/4 → 1/3 → total; 3 elements → 4 → 5)

Moderate: Direction is clear but not all steps show measurable escalation. Weak: Escalation is subjective or some steps don't clearly advance.

Number Pattern Validation

A claimed number pattern is Strong when ALL of: 1. The count is verified from the Greek text (not just English translation artifacts) 2. No items are excluded to make the count work 3. No items are artificially split or merged to reach the target number 4. The same number appears in at least 2 independent contexts in Revelation

Moderate: Count is verified (#1) and honest (#2-3), but the number appears in only one context. Weak: Count depends on debatable inclusion/exclusion of borderline items.

Parallel Sequence Validation (Trumpets↔Bowls, Seals↔Olivet Discourse, etc.)

A claimed parallel is Strong when ALL of: 1. Element-by-element correspondence exists for >75% of items 2. The order matches (elements are not rearranged to fit) 3. Shared vocabulary is documented for each corresponding pair (as VP items) 4. Differences and non-matching elements are honestly noted

Moderate: 50-75% correspondence with order match; some pairs lack verbal links. Weak: <50% correspondence, or order must be rearranged, or differences outnumber similarities.

Chronological Model Classification

Some structural observations bear on how Revelation's sequences relate chronologically. Three competing models:

  • Recapitulation — Evidence that judgment sequences cover overlapping time periods, each presenting the same era from a different angle. Key indicator: multiple sequences ending with Second Coming language.
  • Linear/Sequential — Evidence that sequences follow one another chronologically. Key indicator: "kai eidon" and "meta tauta" as chronological markers; no repeated endpoints.
  • Telescoping — Evidence that later sequences are contained within earlier ones (7th seal → trumpets; 7th trumpet → bowls). Key indicator: 7th element of one sequence transitioning directly into the next sequence; shared theophany formula intensifying.
  • Neutral — Structural observation that does not favor any chronological model.

Classification rules: - Most TM and VP items are Neutral (they describe what's there, not what it means) - SP items often have chronological implications (document them) - IC items frequently address chronological questions directly - The chronological question is primarily addressed in Module 8 studies, using evidence accumulated from all other modules

Important: Chronological model classification is secondary to structural cataloging. The primary purpose of this series is to catalog what the text contains. The chronological model question is ONE application of that catalog, not the organizing principle.

Structural Databases (REQUIRED)

revelation-study.db (Study Analysis Database)

Stores chunked study content for semantic search across the series.

Location: D:/bible/bible-studies/revelation-study.db Script: D:/bible/revs_study_db.py

Standard workflow after completing a study: 

# Ingest the study
python D:/bible/revs_study_db.py ingest D:/bible/bible-studies/revs-XX-slug

# Generate embeddings (or update for new chunks only)
python D:/bible/revs_study_db.py embed --update

Querying prior studies (REQUIRED before starting analysis): 

# Find prior analysis of a specific passage
python D:/bible/revs_study_db.py find-passage "Rev 8:1"

# Find prior word studies
python D:/bible/revs_study_db.py find-word "kai eidon"

# Semantic search
python D:/bible/revs_study_db.py search "throne room structural anchor" --top 5

# Get a specific study summary
python D:/bible/revs_study_db.py get revs-05

revelation-structural.db (Structural Elements Database)

Catalogs all structural observations across the series. This is the deduplication mechanism — each study checks before adding new elements.

Location: D:/bible/bible-studies/revelation-structural.db Script: D:/bible/revs_structural_db.py

Standard workflow for each study:

  1. Check for existing elements before adding new ones: 

    python D:/bible/revs_structural_db.py find TM --ref "Rev 1:10"
python D:/bible/revs_structural_db.py search "en pneumati fourfold vision"

  2. For each structural observation in your analysis:

  3. If a match exists → note the master ID and register your study: python D:/bible/revs_structural_db.py also-in TM001 revs-XX

  4. If no match → reserve the next ID: python D:/bible/revs_structural_db.py next-id TM then add it: python D:/bible/revs_structural_db.py add TM --id TM001 --description "..." --ref-a "Rev 1:10" --chronological Neutral --study revs-01

  5. After all elements registered, generate embeddings: 

    python D:/bible/revs_structural_db.py embed --update

  6. In your CONCLUSION.md, add a note: "Structural elements registered in D:/bible/bible-studies/revelation-structural.db"

Cross-Study References

Within the Series

  • Reference other revs-XX studies by slug when relevant
  • Module 1 findings are foundational — later modules may build on them
  • Use the study DB to find prior analysis: revs_study_db.py find-passage "Rev 8:1"
  • Briefly state what the prior study found and cross-reference it — do not re-analyze

Prior Study Conclusions

Each study should consult prior work before beginning analysis:

Primary method — study database: 

python D:/bible/revs_study_db.py find-passage "Rev 4:5"
python D:/bible/revs_study_db.py search "sanctuary typology" --top 5
python D:/bible/revs_study_db.py get revs-05

Secondary method — read CONCLUSION.md directly for the studies the DB search identifies as most relevant.

No Editorial Opinion

  • Do NOT characterize findings as "proving" any structural model — present the evidence and its validation rating
  • Do NOT call any observation "the strongest" or "the weakest" — present the validation criteria results
  • Do NOT use "clearly shows" or "obviously means" — state what the text contains and what it is consistent with
  • Do NOT impose interpretive schools (historicist, preterist, futurist, idealist) — analyze the text's own structural features
  • For passages covered by other studies in the series, briefly state what the text contains and cross-reference the study
  • State what the text says. Let the structural evidence speak for itself.

Required CONCLUSION.md Template

Every revs-XX study MUST produce a CONCLUSION.md that follows this exact structure. All sections are REQUIRED unless marked (conditional). Use the exact heading levels shown. Do not rename sections, reorder them, or omit any.

# [Descriptive Study Title] (revs-XX)

## Study Question
[The original question from the task prompt — copy verbatim]

## Methodology
This study follows the structural analysis methodology defined in
`D:/bible/bible-studies/revs-series-methodology.md`.
Structural elements registered in D:/bible/bible-studies/revelation-structural.db.

---

## Summary Answer
[2-3 sentence direct answer summarizing what structural features were found.
State what the textual markers and verbal parallels establish.
Do not editorialize — present findings as data.]

## Key Verses
[6-12 most important verses. Format each as:]

**[Reference]** — "[Full KJV verse text]"

[Select verses that represent the most structurally significant findings.]

---

## Structural Elements Catalog

Elements tracked in D:/bible/bible-studies/revelation-structural.db.

### Textual Markers (TM)

**Also-cited prior items** (already in structural DB, cited again by this study):

| Local # | Description | Reference | Master ID |
|---------|-------------|-----------|-----------|
| TM1 | [Observable textual feature] | [Rev X:Y] | [Master ID] |

**New items** (added to structural DB by this study):

| Local # | Description | Reference | Master ID |
|---------|-------------|-----------|-----------|
| TM2 | [Observable textual feature] | [Rev X:Y] | [Master ID] |

---

### Verbal Parallels (VP)

| Local # | Passage A | Passage B | Shared Elements | Link Count | Strength | Master ID |
|---------|-----------|-----------|-----------------|------------|----------|-----------|
| VP1 | [Rev X:Y] | [Rev A:B] | [Listed elements] | [N] | [Strong/Moderate/Minimal] | [Master ID] |

---

### Structural Patterns (SP)

| Local # | Pattern | Based On | Validation | Chronological | Master ID |
|---------|---------|----------|------------|---------------|-----------|
| SP1 | [Pattern description] | [TM#, VP# items] | [Strong/Moderate/Weak] | [Recap/Linear/Telescoping/Neutral] | [Master ID] |

[For each SP, include the validation analysis showing which criteria are met.]

---

### OT Allusion Network (AN)
(conditional — include when OT allusions are identified)

| Local # | Revelation | OT Source | Shared Vocabulary | Allusion Strength | Master ID |
|---------|------------|-----------|-------------------|-------------------|-----------|
| AN1 | [Rev X:Y] | [OT Book X:Y] | [Listed words] | [Explicit/Strong/Probable/Echo] | [Master ID] |

---

### Interpretive Claims (IC)
(conditional — include when interpretive conclusions are drawn)

| Local # | Claim | Based On | Chronological | Master ID |
|---------|-------|----------|---------------|-----------|
| IC1 | [What the pattern means] | [SP#, AN#, VP# items] | [Recap/Linear/Telescoping/Neutral] | [Master ID] |

[For competing IC items, present both with their supporting evidence.]

---

## Tally Summary

- Textual Markers: [count]
- Verbal Parallels: [count] ([N] Strong, [N] Moderate, [N] Minimal)
- Structural Patterns: [count] ([N] Strong, [N] Moderate, [N] Weak)
- OT Allusions: [count] ([N] Explicit, [N] Strong, [N] Probable, [N] Echo)
- Interpretive Claims: [count]

### Chronological Model Indicators (This Study)

| Tier | Recapitulation | Linear | Telescoping | Neutral | Total |
|------|----------------|--------|-------------|---------|-------|
| TM | [count] | [count] | [count] | [count] | [count] |
| VP | [count] | [count] | [count] | [count] | [count] |
| SP | [count] | [count] | [count] | [count] | [count] |
| AN | [count] | [count] | [count] | [count] | [count] |
| IC | [count] | [count] | [count] | [count] | [count] |
| **TOTAL** | **[count]** | **[count]** | **[count]** | **[count]** | **[count]** |

---

## What the Text Shows

**Observable structural features established by this study:**
- [Bullet list — draw ONLY from TM and VP tier items]
- [Use "The text contains..." or "The Greek text shows..."]

## What Requires Interpretation

**Structural claims that go beyond direct observation:**
- [Bullet list — draw from SP and IC tier items]
- [Note the validation rating for each SP item]
- [Note when competing interpretations exist]

---

## Conclusion

[Final synthesis paragraphs. Requirements:
- Cite the structural element counts from this study
- Note pattern validation ratings
- Present competing structural readings when they exist
- Use "the text contains," "validated as Strong/Moderate/Weak," "consistent with"
- Do NOT use: "this proves," "clearly shows," "the strongest evidence"
- Cross-reference other revs-XX studies where relevant]

---
*Study completed: [YYYY-MM-DD]*
*Structural elements registered in D:/bible/bible-studies/revelation-structural.db*

Template Checklist (verify before declaring CONCLUSION.md complete)

The analysis agent MUST verify all of these are present:

  • ## Study Question — original question copied verbatim
  • ## Methodology — methodology file reference + structural DB note
  • ## Summary Answer — 2-3 sentence direct answer
  • ## Key Verses — 6-12 verses with full KJV text
  • ## Structural Elements Catalog — header present
  • ### Textual Markers (TM) — with Master ID column
  • ### Verbal Parallels (VP) — with Link Count and Strength columns
  • ### Structural Patterns (SP) — with Validation and Chronological columns
  • ### OT Allusion Network (AN) — present if allusions found (with Allusion Strength)
  • ### Interpretive Claims (IC) — present if interpretive conclusions drawn
  • ## Tally Summary — counts by tier
  • ## Chronological Model Indicators — tally table
  • ## What the Text Shows — from TM/VP items only
  • ## What Requires Interpretation — from SP/IC items with ratings
  • ## Conclusion — synthesis with element counts and validation ratings
  • All structural elements registered in revelation-structural.db
  • Study ingested in revelation-study.db

Conclusion Tone Rule

The conclusion section of every study MUST: - Present the structural findings as cataloged data - State what the validation criteria produced - NOT use hedging language like "this doesn't prove X" or "this doesn't disprove Y" - NOT editorialize about what the results mean for any interpretive school - Let the structural evidence and validation ratings speak for themselves

Example of what TO write: "This study catalogs [N] textual markers, [M] verbal parallels, and [P] structural patterns. The chiastic arrangement of the seven letters received a Strong validation rating based on [Q] matching pairs with [R]+ verbal links each. The pattern is consistent with both recapitulation and progressive-revelation readings of the letter sequence."

Example of what NOT to write: "This proves the letters are chiastic" or "This is the strongest evidence for recapitulation."