Foundations

The archive begins by recording what exists before deciding what it means. These pages explain the original discovery pipeline and the identities the application builds from its output.

  1. Scanning the archive: traversal, content hashing, embedded metadata, categories, and database ingestion.
  2. Content identity and duplicates: original occurrences, unique bytes, canonical copies, and provenance.
  3. Archive data model: scanner-owned observations, application records, analyses, and curated context.

The scanner and Rails have different ownership. Rails reads raw scanner records and writes enrichment and decisions into its own tables. Re-running or replacing the inventory is therefore a data-reconciliation problem, not a reason to discard application state.

Table of contents

Back to top

Avichive technical guide ยท Source baseline: October 13, 2026

This site uses Just the Docs, a documentation theme for Jekyll.