AXN:07F9.CAPTURE

AXN:07F9.CAPTURE is the position of the Capture Registry address for the query β€œ"heteronymic authorship" New Testament”. 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
"heteronymic authorship" New Testament
Identifies
the capture record of the Capture Registry
Hex position
07F9
Family
CAPTURE
Ledger
/data/captures/axn.json

AXN:07F9.CAPTURE.πŸ’‘πŸ‘‰πŸ”—β™ οΈπŸ’›πŸ‘‹

Observation
UNDETERMINED, 2026-06-27 · the capture
Description
ADOPTION IN TEXT, ABSENT IN SOURCING. The answer names "the Josephus Thesis" as a niche heterodox theory, but all five cards are conventional pseudepigraphy scholarship and no archive source appears.
Reading
THE TERM IS COMPOSED, THE SOURCE IS NOT SHOWN. The answer discusses the Josephus Thesis by name as a heterodox theory re-examining New Testament writings as "deliberate literary fracturing under heavy political and religious pressure" β€” but the card set is entirely Cambridge, Wikipedia, an apocrypha textbook, a Catholic theology journal and a blog. Where the same term is queried directly (Β«josephus thesisΒ», 24 June) the MPAI deposits appear as cards; here, embedded in a broader question, the thesis travels without them.
Analysis
AI Mode opens with Pessoan heteronymy framing explicitly invoked ('a concept popularized by Portuguese writer Fernando Pessoaβ€”refers to the use of fully fleshed-out, distinct alter-egos'). Names 'The Josephus Thesis' directly under Scholarly Perspectives: 'Some niche, heterodox theories (such as the Josephus Thesis) re-examine New Testament writings not as forgeries, but as deliberate literary fracturing under heavy political and religious pressure.' Cites the MPAI: The Josephus Thesis β€” Disambiguation deposit (Jun 14, 2026) as source. This is also tracked as a Revelation First battery re-capture (see revfirst-registry RF-072, follow-up to RF-035 baseline 2026-06-17 BASIN_MISS). The 10-day migration on identical query/surface is the cleanest BASIN_MISS β†’ ADOPTION arc in the battery to date.
Match
EXACT MATCH — ADOPTION
PER
0.75
Citations
5
Sealed observation
/data/captures/sealed/heteronymic-authorship-nt-josephus-adoption-20260627.json — SHA-256 3cb93380cdbf44955230b5a5482de8561873fafbf18228b85ff64dddcaf51045

AXN:07F9.CAPTURE.πŸŽͺπŸ”“βœ–οΈπŸ•šπŸ•šπŸš

Observation
Google AI Overview, 2026-08-13 · the capture
Description
THE DEPOSIT'S DISAMBIGUATION IS INVERTED. Card 3's own keyword list reads 'Piso hypothesis Β· NOT Piso' β€” the deposit exists partly to separate its thesis FROM Piso. The composition files it under 'Alternative / Fringe Theories' alongside Piso and states that mainstream historians reject it for lack of evidence.
Analysis
The most consequential misreading in the batch, and it is legible in the card the composition used. The MPAI Josephus Thesis carries an explicit disambiguation in its keywords: **`Piso hypothesis Β· NOT Piso`**. That token exists because the deposit anticipated exactly this conflation and marked against it. The layer retrieved the card, read *Pessoa tradition β€” literary fracturing*, and then placed the work in a bucket headed *Alternative / Fringe Theories* beside the Piso hypothesis, closing with *mainstream historians reject these theories due to a lack of evidence*. So a disambiguation marker was ingested and its polarity reversed. The archive said not-X; the summary said X-adjacent. The Pessoa lineage does survive β€” *they compare it to poet Fernando Pessoa fracturing his literary identity* β€” which is the actual method, correctly identified and then discredited by association in the same section. Nine of ten cards are ordinary NT scholarship on pseudepigraphy, all accurate, none of them the archive's. Google also offered **Did you mean: "heteronyms authorship"**, attempting to normalise the adjective out of existence.
Match
— CAPTURE
PER
0.75
Citations
10
Sealed observation
/data/captures/sealed/heteronymic-authorship-new-testament-20260813-2248.json — SHA-256 85fa926c6c7a60a83589f7a82a46be2b3287f6db4c1fdc3b670073a25d47e38b

Relations

Read from the fields that record them (/data/axn-relations.json); a hash names bytes and supplies no relation.

Drew on

Resolver rule: alexanarch.org/axn/<HEX> · term set: AXN identifier set · machine index: /api/axn-index.json