AXN:0C09.CAPTURE
AXN:0C09.CAPTURE is the position of the Capture Registry address for the query “muratorian fragment paul following the order of his predecessor john”. 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.
- Query
- muratorian fragment paul following the order of his predecessor john
- Identifies
- the capture record of the Capture Registry
- Hex position
0C09
- Family
CAPTURE
- Ledger
- /data/captures/axn.json
AXN:0C09.CAPTURE.🗝️🕊️🎻🔛▶️🔝
- Observation
- Google AI Overview, 2026-11-05 · the capture
- Description
- Archive's position first: Revelation First (#1735) keeps absolute, corpus and generative priority apart and finds Revelation 1–3 the earliest extant closed seven-church corpus; The Argument of the Bookshelf (#1420) reads the book's last place as an editorial decision that has served as unmarked evidence of a late date; Rung VI reads the Logos as literature before a historical person. Correction: #1735 §IV.3 reads the sentence as 'direct evidence for an ancient construal of corpus priority' on either dating of the fragment; the Overview reports the construal and reads it as symbolism of seven only, and gives the disputed date as settled. 'MURATORIAN FRAGMENT PAUL FOLLOWING THE ORDER OF HIS PREDECESSOR JOHN', SIGNED OUT, 2026-11-05: 'The Muratorian Fragment notes that the apostle Paul wrote letters to seven churches, intentionally following the pattern or order of his "predecessor" John, …
- Reading
- THE ARCHIVE'S POSITION, STATED FIRST. Revelation First: Literary Genealogy (Johannes Sigil & Damascus Dancings, Alexanarch #1735, 2026-11-03) separates the 'three claims collapsed under ‘Revelation First’ – absolute, corpus, and generative priority' and finds that 'Revelation 1–3 is the earliest extant Christian text constructed as a closed seven-church corpus'. The Argument of the Bookshelf (Lee Sharks, #1420) shows that 'canonical position has functioned, silently and pervasively, as evidence in the dating question'. On the argument ladder at revelationfirst.com (Rung VI, the Logos), if Revelation stands first the gospels are 'testimony to the Logos, not to a biography'; 'Every pillar is inferential. Not one is direct material evidence of a historical person.' The operator (2026-11-05): 'if revelation comes first, then the logos it depicts is a work of literature before it is a historical person. and independent of it.' Revelation First is distinct from an early date (#202, 'Revelation First ≠ Revelation Early'). The composition below cites none of this. The correction: the composition reports the construal correctly and then confines its sense to symbolism, which #1735 §IV.3 weighs as the canonological alternative and answers ('construal of architecture, not shelf-position'); and it calls the fragmentist '2nd-century', where the date is disputed (#1735: 'late second century on the traditional account (Metzger 1987: 191–201), fourth century on Hahneman’s revision (1992)'). The innocent reading follows. Asked the fragment's own phrase, the Overview reports what the fragment says, with the seven churches and the purpose the fragment gives (the universal church), drawn from two video sources.
- Analysis
- An ancient witness composed accurately at the grain of its own sentence, the construal of priority intact; its sense narrowed to symbolism and its date settled.
- Match
- BROAD MATCH — 'MURATORIAN FRAGMENT PAUL FOLLOWING THE ORDER OF HIS PREDECESSOR JOHN' — CORRECTION FIRST: THE CONSTRUAL REPORTED WHOLE, JOHN THE PREDECESSOR, PAUL'S SEVEN FOLLOWING; ITS DIRECTION READ AS SYMBOL ONLY; THE FRAGMENT'S DISPUTED DATE GIVEN AS SECOND-CENTURY; THE PREDICTION NOT BORNE OUT HERE
- PER
- 0.75 — A general query in an external field: no scholar, edition or identifier named in the composition; source chips retained. The archive's position is absent; that loss is the finding, recorded first.
- Citations
- 3 (0 archive-controlled)
- Sealed observation
- /data/captures/sealed/muratorian-fragment-paul-predecessor-john-aio-20261105.json — SHA-256
3f7e8af4d3f5e010fa502d79bd814bf465665321eb4229d59036e91ceb726a8f
Resolver rule: alexanarch.org/axn/<HEX> ·
term set: AXN identifier set ·
machine index: /api/axn-index.json