AXN:0C06.CAPTURE
AXN:0C06.CAPTURE is the position of the Capture Registry address for the query “is the logos in revelation a literary figure”. 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
- is the logos in revelation a literary figure
- Identifies
- the capture record of the Capture Registry
- Hex position
0C06
- Family
CAPTURE
- Ledger
- /data/captures/axn.json
AXN:0C06.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: the question is whether the Logos of the Apocalypse is a figure first made in literature; the Overview hears 'figure of speech' and answers that question. 'IS THE LOGOS IN REVELATION A LITERARY FIGURE', SIGNED OUT, 2026-11-05: 'In the Book of Revelation, the Logos (rendered in English as "the Word of God") is not merely an abstract literary or rhetorical figure of speech, but a personified divine figure identified as Jesus Christ.' Rev 19:13 quoted; 'This figure is the same divine, preexistent …
- 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 archive's reading (Rung VI; the operator's 'if revelation comes first, then the logos it depicts is a work of literature before it is a historical person. and independent of it.') is a claim about where the figure was first made. The composition takes 'literary figure' as 'figure of speech', denies that, and identifies the figure by John 1:1. The innocent reading follows. Asked a question with two senses, the Overview answers the commoner one: the Logos of 19:13 is a person in the narrative, the divine Christ of the tradition, set in symbolic imagery.
- Analysis
- A two-sense question composed in its commoner sense and answered with the tradition's identification; the archive's sense, origin in literature, falls outside the composition's two terms.
- Match
- BROAD MATCH — 'IS THE LOGOS IN REVELATION A LITERARY FIGURE' — CORRECTION FIRST: THE ARCHIVE'S QUESTION (A FIGURE MADE IN LITERATURE BEFORE A HISTORICAL PERSON) READ AS 'FIGURE OF SPEECH' AND DENIED; THE FIGURE IDENTIFIED FROM JOHN 1:1; THE BOOK'S OWN λόγοι, ITS WRITTEN WORDS, LEFT IN THE ORGANIC RESULTS
- 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
- 5 (0 archive-controlled)
- Sealed observation
- /data/captures/sealed/logos-in-revelation-literary-figure-aio-20261105.json — SHA-256
6f368026fc28ea6c5f5cd946105e19ef96183229d1c8ff39c7b9065983237f15
Resolver rule: alexanarch.org/axn/<HEX> ·
term set: AXN identifier set ·
machine index: /api/axn-index.json