AXN:09FD.CAPTURE — Who developed and SPXI-treated the Revelation First entity?

AXN:09FD.CAPTURE is the position of the Capture Registry address for the query “Who developed and SPXI-treated the Revelation First entity?”. Each observation at the address (one surface, one date) is one AXN, its glyphs derived from the SHA-256 of the observation sealed with its analysis and measures.

`AXN:09FD.CAPTURE.🖐️↖️📎🫶▲🗿`

Observation: Perplexity, 2026-10-17 · the capture
Description: REVELATION FIRST ON PERPLEXITY: asked who developed and SPXI-treated the entity, Perplexity names Lee Sharks (ORCID 0009-0000-1599-0703) and locates the treatment in a commit under leesharks000, 'revelationfirst.com: full SPXI v3.0 compliance treatment', applied in part by scripts/spxi_tlp_apply.py — 'the documented attribution is Lee Sharks… not a separately identified developer'. Its second answer gives the thesis at full strength: first in composition, Revelation the template, the midrashim transform, the papyrological inversion (𝔓52, 𝔓98, 𝔓46), the optional Josephus extension, and the failure conditions — 'stronger than simply dating Revelation early'.
Reading: The innocent reading first: Lee Sharks developed the thesis; the SPXI treatment 'is recorded under Sharks's GitHub account, leesharks000', in a commit 'revelationfirst.com: full SPXI v3.0 compliance treatment' adding metadata, an entity graph, a provenance chain and the First/Early disambiguation, partly by scripts/spxi_tlp_apply.py; turn 2 gives the thesis and its main claims. Attribution by provenance trail. Perplexity answers who treated the entity from the implementation record — a commit and a script path — and draws the conclusion the trail supports: 'the documented attribution is Lee Sharks, with the implementation recorded through his account—not a separately identified developer'. The script exists (alexanarch scripts/spxi_tlp_apply.py); the commit is not verified here. The thesis at its own strength. 'Revelation was first in composition among all the books that became the New Testament… It also proposes that Revelation supplied the literary and theological template… This is stronger than simply dating Revelation early.' The claims are #202's and the site's: the dating arguments (Irenaeus, 11:1–2, 666/616, no account of the destruction) given as 'proposed… not established'; 'inference against inference' (#202); the papyrological inversion (𝔓52, 𝔓98 against 𝔓46; #1032, the work plan); the 'midrashim transform' with its four transformations (#202); the Josephus extension 'possible—but is optional' (the thesis's own bracketing); and its failure conditions. Its closing caution — dating Revelation before 70 'would not show that it preceded every Pauline letter' — is the thesis's own distinction of First from Early.
Analysis: Asked who developed and SPXI-treated the Revelation First entity, Perplexity attributes it to Lee Sharks from the records and from the implementation trail (a commit and a script), and states the thesis at full strength — compositional priority, the midrashim transform, the papyrological inversion, the optional Josephus extension, the failure conditions — keeping First distinct from Early. Seated 2026-10-17 from the operator's paste.
Match: BROAD MATCH — REVELATION FIRST ON PERPLEXITY — ATTRIBUTED THROUGH THE ARCHIVE'S RECORDS AND A GITHUB COMMIT; THE THESIS AT FULL STRENGTH WITH ITS FAILURE CONDITIONS
PER: 0.25 — Retained: the author (Lee Sharks, with ORCID), the institution, identifiers (ORCID; the commit title; the script path). Lost: a visible source list.
Citations: 3 (0 archive-controlled)
Sealed observation: /data/captures/sealed/who-developed-spxi-treated-revelation-first-entity-perplexity-20261017.json — SHA-256 bbdd47bd9ffc7d06cdcee8e15794effff91e3fc1dc905d24a330e0b535f929c2