# Audit - @666ab731 archive coverage, redirect alias, and late public recoveries

## Index integrity

- Canonical index: `solution/tweets/666ab731-timeline.json`
- SHA-256: `a78b4dd2cb723e8823c10bac3f1a5ed265604bdf3a649e361764ed8463e0b1f2`
- Canonical recovered bodies: `95`
- Known tombstones: `4`
- Duplicate canonical IDs: `[]`
- Snowflake / displayed-time mismatches: `[]`
- Author-labelled rows in the retained status-ID discovery index: `90`
- Discovery IDs absent from the canonical index: `['1427682189223813123']`

Every retained post ID has a Snowflake timestamp within one second of the
stored UTC timestamp. This is an integrity check on the index, not a claim
that all account posts were discoverable. The retained status-ID index has
only one noncanonical row: the redirect alias adjudicated below. Three later
profile-link discoveries, two screenshot-backed 2017 replies, and the Wayback-recovered status sit outside that
immutable index. Their provenance is preserved rather than silently spliced
into the old discovery harvest.

## Redirect alias removed on 27 July 2026

- Apparent 2021 ID: `1427682189223813123`
- Snowflake timestamp: `2021-08-17T17:22:13.620Z`
- Wayback capture: `https://web.archive.org/web/20210817173307id_/https://twitter.com/666ab731/status/1427682189223813123`
- Archived original response: `302` -> `https://web.archive.org/web/20210817173307id_/https://twitter.com/666ab731/status/976500950046265344`
- Public syndication lookup for the apparent ID returned: `976500950046265344` at `2018-03-21T16:49:03.000Z`

Both public routes resolve the apparent 2021 ID to the canonical 2018 Bennu
tweet. Keeping both records would publish the same payload twice under
incompatible dates, so the redirect alias remains excluded from the canonical index.

## Three late public-syndication recoveries

- Provenance file: `archive/recon/twitter-account/late-public-syndication-discoveries-2026-07-27.json`
- SHA-256: `0d70086940cead61f39f808a12415387fb3f8c927cc6354efe95f898c42d9f9d`
- IDs: `1822159298341835072, 1914903753121054906, 1925824081816924585`
- Discovery boundary: public profile detail links supplied the IDs; the recorded
  texts came from X's public syndication endpoint and each raw response hash is
  retained in the provenance file.

## Two 2017 screenshot-backed reply recoveries

- Provenance file: `solution/tweets/hive-screenshot-recovery-audit.json`
- SHA-256: `edffd5e094800ad855d0f9e48d02733268a2f8d63e1ef9a58951912bc0240eac`
- IDs: `851669304642863108, 852785208839487488`
- Evidence boundary: each saved public syndication response supplies the exact status body, UTC, author handle, and parent ID; a retained Hive/Steemit screenshot independently corroborates the historical conversation.

## Former tombstone recovered through Wayback

- Status ID: `1388787664829177860`
- Snowflake timestamp: `2021-05-02T09:29:16.379Z`
- Wayback capture: `2021-05-02T09:29:43Z` - `https://web.archive.org/web/20210502092943id_/https://twitter.com/666ab731/status/1388787664829177860`
- Exact text: `BC1YLh9rZjcRTDhfC7JHzXikQt9AT1N3rWC7XGHpCdoqEGN288EY9Md #bitclout #BitCloutVerifyMe`
- Saved HTML: `archive/recon/twitter-account/bitclout-recovery-2026-07-27/tweet-1388787664829177860-wayback-20210502092943.html` - SHA-256 `5dec9ae1d440f0e508e4559ea22153ed483693389c8b468179d9c08b4107ce0d`

A current public syndication lookup had no body for this ID, but its
near-contemporaneous Wayback permalink HTML retains the exact post text. It is
therefore a recovered canonical tweet, not one of the remaining tombstones.
The linked BitClout/DeSo branch is documented separately; it supplies Page-23
context but not a cryptographic identity bridge or a new cipher key.

## Remaining coverage boundary

The profile count captured on 2026-07-26 was
`132`. With `95` canonical
bodies and `4` identified-but-unreadable posts, at
least `33` posts are still
unrecovered or were never discovered by the archive enumeration. The count may
not be directly comparable across all X post types, so this is a lower bound.

The four remaining known tombstone IDs were rechecked through the public
syndication endpoint on 27 July 2026. All still returned tombstones with no body.

## Consequence for the lore timeline

The correction does not remove any 2016-2018 source text: the valid 2018
Bennu hex post remains in the index. It prevents a false 2021 continuation
from being inferred from a redirect/cache alias, while restoring a different
real 2021 continuation from its own Wayback capture. The unidentified coverage
gap remains a high-value archival target, but cannot be filled by guessing posts
from Snowflake ranges.