Forty-eight manifests do not mean forty-eight independent witnesses.
UL's archive arrived in waves: split ZIPs, repaired tails, overlapping exports, handoff briefs, screenshots, secondary copies, and bots documenting what another bot already documented. Source custody is the part where we stop the evidence locker from developing multiple personalities.
The later Wall package is the chronology owner because it extends the earlier complete 2020–2025 corpus through August 11, 2026. The earlier package remains useful for inspected visual/icon provenance. Same room, overlapping evidence, one longitudinal story.
BOUNDARYDo not add 12,995 + 13,011 and call it 26,006 Wall messages. The later corpus overlaps the earlier one.
Poster Dump and Club Media Gallery are the primary PR corpora. Character-Bible/PR/Slice text handoffs and deploy-log bundles are derivative summaries of this work, not extra witnesses. Use the raw PR owner for receipts; use the handoffs only to understand prior processing decisions.
BOUNDARYPoster Dump's local uploader=creator exception does not silently migrate into Club Media Gallery or the rest of the archive.
The recovered transcript contains 31,875 messages for 2020–2021; later tail recovery carries Slice through the final split disk and adds direct 2022–2026 material. The transcript is physically in z81, not z82. Old handoffs saying to continue after z90 are superseded by the later completed tail recovery.
BOUNDARYOne historical media volume, z51, remains absent. That is a media hole, not permission to call the transcript incomplete.
Several intake folders cover different Whiskey eras. They are one longitudinal room, not several independent communities. Complete transcript periods can be used directly; media-partial periods keep their visual boundary; a complete-empty export is an archive state, not proof nobody spoke elsewhere.
BOUNDARYCombine by Discord message identity and time boundary before making counts or recurrence claims.
The authoritative reunion ZIP resolves 3,980 raw message copies to 2,736 unique Discord messages through August 18 and now owns the recovered visual/video layer too. The smaller Aug. 9 and Aug. 14 ZIPs add zero unique SHA-256 payloads outside that superset, and the earlier living-ensemble packet remains overlap rather than a second witness.
BOUNDARYComplete means the recovered ZIP boundary is accounted for. Four unjoined cache payloads remain unattributed and are not evidence; development screenshots and reunion recollections still do not become appointment chronology.
Two partial intakes currently form one contiguous media run through z32. The images are rich enough for visual genre findings, but the Discord transcript and final archive boundary have not arrived in this corpus state.
BOUNDARYA Raja share card can identify the source game account. It does not automatically identify the Discord uploader, photographer, every avatar, or a real relationship between co-stars.
Multiple intake folders contain the same Character Bible, PR analysis, Slice continuation brief, tracker notes, UI screenshots, or deploy logs. They document prior work. They do not multiply confidence merely because the same sentence survived in six folders wearing different timestamps.
BOUNDARYDerivative summaries never outrank their primary transcript/media owners or Mugs-confirmed canon.
A person can post somebody else's drawing. A game share card can identify a source account without naming the Discord uploader. A screenshot can feature twelve people without proving who captured it. A derivative handoff can correctly repeat a fact without becoming a second primary source. The archive keeps those verbs separate because collapsing them is how innocent bystanders become art directors.
The integration sidecars are the live boundary map. The August reunion media review is now closed for the recovered ZIP set; packets still marked partial elsewhere remain partial until their own named reopening condition changes.
This page describes current custody and overlap rules, not a claim that every UL archive ever made is present. COMPLETE means complete for the validated package boundary described by its manifest plus current integration sidecar. BLOCKED and PARTIAL corpora remain bounded as such. When a later intake supersedes an earlier recovery instruction, the earlier document remains historical processing evidence rather than active extraction guidance.