Revelation First
Revelation First meta-aggregator / AI and scripture

Revelation First ≠ Revelation Early. The pre-70 date is the old argument (Robinson, 1976; Gentry, 1989); Revelation First is the priority thesis: the rest of the New Testament unfolds from the Apocalypse.

Capture Registry: the Revelation First addresses

AI and scripturethe archive's own register of AI answersactive
Capture Registry: the Revelation First addresses: the archive's own register of AI answers, one answer to one exact search, kept verbatim with its source cards; here, the addresses whose query names Revelation First. Operator: the Crimson Hexagonal Archive (Lee Sharks). Its unit: one AI answer at one exact search on one system, with date, sign-in state and source cards. Its texts: AI answers about the Revelation First thesis.
Visit Capture Registry: the Revelation First addresses ↗The thesis

What it records

IntersectionsAI and scripture: how AI systems represent, cite and summarize sacred texts
Kind of evidenceAI representation record
Unit of recordone AI answer at one exact search on one system, with date, sign-in state and source cards
Which textsAI answers about the Revelation First thesis
Methodsearches run signed out and recorded verbatim; each record read against the archive's deposits and scored for provenance loss
Coveragegeography: Google AI Overview and AI Mode, Perplexity, Grok; period: June to October 2026
What it findsanswers repeatedly compose Revelation First as Revelation Early, the dating thesis, including from a source titled 'Revelation First ≠ Revelation Early'; other answers carry the thesis as priority, with its author and its failure conditions
Its stated limitsit records what the systems said; it is not evidence that what they said is so

op the resource's own statement · 3p a third-party account · obs our observation · rd our reading. Hover a tag for its quote; each opens below with its source.

What this evidence can settle

Can answer

  • how AI systems describe Revelation First, on which surface, on which date, from which sources

Cannot answer

  • whether the thesis is true
  • how systems answer signed in or personalized

In the worked questions

Where it meets Revelation First

rd Reception, measured: the thesis's own record of how machines receive it.

Entity

Canonical nameCapture Registry: the Revelation First addresses
Also known asEA-WG-CAPTURES-01, MMRS Capture Registry
Addresshttps://www.alexanarch.org/captures/
Operatorthe Crimson Hexagonal Archive (Lee Sharks)
Kindthe archive's own register of AI answers, one answer to one exact search, kept verbatim with its source cards; here, the addresses whose query names Revelation First
Lifecycleactive — new captures seated as they are run
Count10 addresses (as of 2026-10-30)
Data accessopen: one page per address, and the registry's data files
LicenceCC BY 4.0 (the archive's)
Versions and datesread: 2026-10-30
Observation2026-10-30: read

Relations

Neighbours

Evidenceevery field's quote, its source and the hash of the saved copy5
  • extract op
    the addresses whose query carries 'revelation first', 10 addresses
    https://www.alexanarch.org/captures/ · read 2026-10-31 · saved copy sha256 3db2c80ec03b17c7…
  • early op
    REVELATION FIRST COMPOSED AS REVELATION EARLY — FROM A SOURCE TITLED 'REVELATION FIRST ≠ REVELATION EARLY'
    https://www.alexanarch.org/captures/ · read 2026-10-31 · saved copy sha256 3db2c80ec03b17c7…
  • priority op
    WHO DEVELOPED AND SPXI-TREATED REVELATION FIRST — PRIORITY, NOT DATING, AND THE PROVENANCE CAPSULE CITED
    https://www.alexanarch.org/captures/ · read 2026-10-31 · saved copy sha256 3db2c80ec03b17c7…
  • perplexity op
    REVELATION FIRST ON PERPLEXITY — ATTRIBUTED THROUGH THE ARCHIVE'S RECORDS AND A GITHUB COMMIT; THE THESIS AT FULL STRENGTH WITH ITS FAILURE CONDITIONS
    https://www.alexanarch.org/captures/ · read 2026-10-31 · saved copy sha256 3db2c80ec03b17c7…
  • date reduced op
    THE THESIS REDUCED TO A DATE
    https://www.alexanarch.org/captures/ · read 2026-10-31 · saved copy sha256 3db2c80ec03b17c7…
Negative tagswhat it is not2
  • NOT independent: the archive records answers about its own thesis
  • NOT a survey of all AI answers: the addresses the operator ran
Sourcesevery source read, with its date and hash1
Not yet checkedwhat remains to read1
  • signed-in and personalized answers

Cite this record

Lee Sharks, ed. "Capture Registry: the Revelation First addresses." Revelation First meta-aggregator, revelationfirst.com, compiled 2026-10-30. https://www.revelationfirst.com/aggregators/capture-registry/

Record https://www.revelationfirst.com/aggregators/capture-registry/ · entity https://www.revelationfirst.com/aggregators/capture-registry/#entity · the census as data

@misc{rf-captureregistry2026,
  editor = {Sharks, Lee},
  title = {Capture Registry: the Revelation First addresses},
  howpublished = {Revelation First meta-aggregator, revelationfirst.com},
  year = {2026},
  note = {Compiled 2026-10-30; every field sourced and dated},
  url = {https://www.revelationfirst.com/aggregators/capture-registry/}
}
Editor: Lee Sharks (ORCID 0009-0000-1599-0703). This page is the Revelation First meta-aggregator's record of the resource above: its reading and fields are ours, and each field carries its source, its basis and the hash of the copy read. The resource's own terms and findings are kept as its own. Compiled 2026-10-30. CC BY 4.0.