TightBeatz.comThe TightBeatz Archive

History, music, people, forums and surviving receipts

Archivist and data lane

For archivists / data

This is the public front door for the archive's data files. The exhibit pages are for reading the history; these files are for review, citation, search tools, LLM grounding, validation and preservation work. They do not include private Discord captures, submitted media payloads, current-account bridges, local evidence paths, raw lyrics, uploads, comments or user accounts.

Open catalog JSONOpen schemaValidation reportAI guidellms.txt

Start here

Human archive
/start-here.html and /what-tightbeatz-was.html explain the scene before the data.
Public catalog
/catalog/ is the browseable public index across people, music, forum, oral history and evidence records.
Canonical JSON
/catalog/catalog.json is an object with release metadata and a records array. Use stable record ids and item URLs when citing it.
AI and crawlers
/ai.html and /llms.txt tell LLMs and crawlers how to preserve uncertainty, survival labels and rights boundaries.

Public data files

Catalog JSON
catalog/catalog.json - all public records, including stable ids, titles, sections, source fields, survival state, evidence class, confidence, completeness, rights notes, relationships and public item URLs.
Catalog schema
catalog/schema.json - the current public catalog contract. It documents normalized fields without removing older compatibility fields.
Validation report
catalog/validation-report.json - build-time validation results for required fields, ids, relationships, source URLs, image paths and normalized values.
Data quality report
catalog/data-quality-report.json - known quality warnings and honest gaps that should not be smoothed over.
Catalog summary
catalog/catalog-summary.json - public counts by section, type, evidence class, survival state, confidence, era, playability and other review dimensions.
Graph export
catalog/graph.json - lightweight nodes and typed relationship edges for network review.
Collection index
collections/collections.json - generated public collection definitions and route pointers.
Collection schema
collections/schema.json - generated collection-file contract.
Collection validation
collections/validation-report.json - collection build checks and member-record coverage.
Random record
random-record.json - compact public endpoint for choosing a random public record without exposing hidden material.
Release manifest
archive-manifest.json - public-release scope, counts, routes and exclusion boundaries.
Sitemap and robots
sitemap.xml and robots.txt - crawlable public routes and crawler rules.

Fields to preserve

  • survivalState says whether the item survived, survived partially, is metadata-only, is external-only, is missing or is unknown. Missing records are not playable media.
  • evidenceClass separates archival captures, direct media, public metadata, external traces, participant memory, community memory and inference.
  • confidenceClass is the confidence label. Confirmed, high, medium, low and inference records should not be summarized as the same proof level.
  • sourceOwnership says whether the source is first-party TightBeatz, member-controlled, third-party, archive-service, community-submitted, archive-curated or unknown.
  • relationships are typed links between records. A mentions relationship is context, not automatic artist credit.
  • rights and source fields control reuse. A public source link is not permission to download, monetize or rehost media.

Reuse boundary

  • Cite item pages or record ids instead of inventing cleaned-up titles, names or credits.
  • Keep handle-first identity. Do not merge current accounts, private submissions or real-name bridges into original-era proof.
  • Do not publish private Discord context, submitted media payloads, local preservation paths, current contact fields, raw lyrics or private-room material.
  • Do not claim the archive has playable audio where the record is metadata-only, missing, external-only or an open lead.
  • Use corrections and rights for takedown, credit, attribution, privacy and stronger-source updates.