History goes to Drive. A chain fact goes to a Base or Zora read. A receipt goes to GitHub. Doctrine stays in the repo that states it. A proof root is only where a document explicitly binds it.
COUNT_DELTA = 9
MEMBERSHIP_DELTA = PROVEN
SET_COMPARISON_MATCH = TRUE
CHECKPOINT_SEALED = FALSE
SEALING_RAIL = UNDEFINED
MATCH + LOCAL_MARKER ≠ SEALED_CHECKPOINT
COUNT_RECHECK = PENDING
AL = UNRESOLVED
Three lanes
1,015 to 1,024 matched as a set. A local seal, a status, a raise, or an unpersisted hash does not seal it. The sealing rail is not defined and has not been run. Not canon. FLOCKZOOM is outside the next epoch.
Where a question goes
COMPUTERWISDOM is the operations root, not the universal proof root. AL is called a proof machine in ROOT_BINDING.md, 2026-07-03, and a doctrine layer in docs/master_jsonwisdom_repo_graph_v1.md. Neither reading wins yet.
Four populations
Contract address was the key. 1015 are in both. 0 were removed. 9 are only in the live mirror. Checked metadata conflicts: 0. Fields: title, description, image_uri, zora_url, created_at, chain. The nine rows below are that only-in-mirror set, and they are also the rows dated on or after September 2. FLOCKZOOM is in neither set. The mirror still ends September 10. The 72-row profile gap was not a loaded set.
CHATGPT_DRIVE_RECOVERY = ENABLED
HISTORY_CLOSED = false · title miss ≠ absence
This pass
Both folders were on the Jason Wisdom Drive this connector searched. A second account was checked by you. It was not separately enumerated here, so that check stays yours.
Context search, not the title
The Zora Reverse Replay that was opened is a 2025-03-31 to 2025-04-30 slice. Its source file has 857 rows and ends 2026-05-01. That is not the 1,015 baseline, and it does not reach September 25. No FLOCKZOOM string was in that document. A miss here still does not close the coin.