AXN:0888.CAPTURE — what is the crimson hexagonal archive?

AXN:0888.CAPTURE is the position of the Capture Registry address for the query “what is the crimson hexagonal archive?”. 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:0888.CAPTURE.🪐⏏️↗️☉🕛🔙`

Observation: Perplexity (agentic), 2026-08-21 · the capture
Description: AN AUDIT, NOT A DESCRIPTION — asked what the archive is, the surface fetched three datasets, wrote reconciliation code, and disagreed with the site's own published figure. Counts verified exact. One error: a correct count at the wrong unit.
Reading: An AUDIT event rather than a composition event, and the first in the registry. Asked what the archive is, the surface fetched three datasets, wrote reconciliation code, ran it, caught its own 200KB fetch truncation and re-fetched via curl, consulted a reviewer, applied fixes, and produced a report with a per-file appendix. VERIFIED EXACT against the live data: 999 files, 132.99 MB, 958 carrying registry IDs, 871 registry assets. AND IT DECLINED TO REPRODUCE THE SITE'S OWN FIGURE: with the downloads page's '97% reconciled' in front of it, it reported its own computation of 95.9% and flagged the discrepancy rather than matching the number it was reading. That is the finding — a layer measuring the archive and disagreeing with it.
Analysis: One error, of a kind the batch specifies. The body_status distribution (truncated 442, severely_truncated 362, partial 120, complete 34) does not match the registry, which holds severely_truncated 341, truncated 336, partial 120, complete 70, unknown 4. The reported totals sum to 958 — the count of FILES carrying registry IDs, not the 871 ASSETS. It counted status per matched file and reported it as the registry distribution: A CORRECT COUNT AT THE WRONG UNIT, presented as a fact about a different object. This is the Atomic Token Rule failure (Erasure Skew v3 §3) occurring in an auditing layer. It also understates 'complete' by half. Separately, its 77 size-drift finding is REAL and was actionable — but undercounted: its GitHub tree was truncated at 1,000 blobs where the full tree holds 1,440. The true figure is 84, since refreshed.
Match: BROAD MATCH — CAPTURE
PER: 0.0
Citations: 0
Sealed observation: /data/captures/sealed/perplexity-cha-reconciliation-audit-20260821.json — SHA-256 0df8daa76df36e9aecfd6f1e4d7fd5ead0e99fd72b68db6200ff7a3e78704442