Research Methods & Source Notes

Methodology, access constraints, and source-note taxonomy used for BREAD archival claims.

Last updated 2/14/2026

Why this page exists

The in-repo research found meaningful materials, but platform access constraints (notably Instagram/RA anti-bot protections) prevent universal direct review from this environment.

This page standardizes how claims should be represented until event-level sourcing is complete.

Source types currently in use

Indexed snippets quoting public social metadata.
SoundCloud profile and repost/playlist traces.
User-provided screenshot extractions.
User-supplied canonical archive notes and link directories.

Known access constraints

Resident Advisor links were often blocked by Cloudflare (403 / anti-bot).
Instagram profile/post access frequently required login or hit automation walls.
Some SoundCloud URLs returned constrained HTTP responses even when metadata could still be recovered.

Source notes taxonomy

Use this per claim/event/person field:

published — directly confirmed from accessible primary source in-repo.
strong — supported by multiple independent signals but not fully bound to primary artifact snapshots.
user-archive — present in user-supplied canonical notes, pending line-by-line review.
open — plausible but not yet source-backed in this repo.

Next review workflow

Create event records with source refs (flyers, event pages, posts).
Bind roster claims to specific artifacts and dates.
Promote source-note labels upward as source material is attached.
Keep unresolved items explicit instead of silently omitting them.