The Library Is the Argument

Where the archive stops being a folder

The Library surface is what the whole quest has been building toward, made browsable: the collection as cards, grouped by maker, each carrying its status, its variants, and its state of preservation. When you look at it below, you are not looking at a file manager with better styling — you are looking at the archive's argument rendered as an interface: this is what we hold, organized by whose hands made it, with each holding's trust story one click away.

The Woodpile Library surface: model cards grouped under maker headings, each card carrying its preservation status, variant label, file list, stored path, and verification date. — The archive's argument as an interface: provenance is the grouping axis, and every status chip is a claim the records back.

The grouping axis is the design decision that carries the most meaning. Files organize naturally by path or date; the Library refuses both and groups by maker — mirroring the upstream namespace — the same maker identity the naming layout records as its root, whatever the storage paths themselves look like (paths may flatten; the maker axis does not). The hierarchy states the archive's priorities in their order: provenance first, everything else second. It is the same axis the review desk scores trust on, because it is the axis that survives — paths change, dates blur, makers are who made the thing.

What a card must answer

Each card is the catalog's front page for one model line, and it earns its place by answering the acquisition questions without opening anything: current preservation status, the variant label and its files, the stored path and revision, and the verified date — integrity as the card's backing record. A card that cannot answer those questions is a thumbnail; the Library's cards are summaries of records.

And the records underneath are the difference between this surface and any file listing: status chips are backed by verified digests, not file presence; "preserved" means the chain closed, not that bytes exist somewhere. The card is a promise the records keep.

A catalog is the archive's memory made visible. Group by provenance, summarize honestly, and make every chip a claim the records can prove — that is the difference between a library and a listing.

Reading your own collection this way

You do not need the app to benefit from the shape. Ask of your current holdings: could I render them as maker-grouped cards where every status is backed by a digest and every variant is labeled as what it is? The gaps that surface — no license recorded, variants indistinguishable, statuses unverified — are the catalog work that matters, and it is exactly the NOTES-and-SHA256SUMS discipline from the archive-design track, viewed from the UI side.

Code

Draft your library cards from the tree·bash

# Render a maker-grouped card listing from a conventional layout:
for maker_dir in archive/*/; do
  echo "== $(basename "$maker_dir")"
  for model_dir in "$maker_dir"*/; do
    [ -d "$model_dir" ] || continue
    n_sum=0; n_ok=0
    for rev_dir in "$model_dir"*/; do
      [ -f "$rev_dir/SHA256SUMS" ] && n_sum=$((n_sum+1))
      grep -q "license:" "$rev_dir/NOTES" 2>/dev/null && n_ok=$((n_ok+1))
    done
    printf '   %-40s revisions:%d  digest-recorded:%d  license-noted:%d\n' \
      "$(basename "$model_dir")" \
      "$(find "$model_dir" -mindepth 1 -maxdepth 1 -type d | wc -l | tr -d ' ')" \
      "$n_sum" "$n_ok"
  done
done
# Every zero in the last two columns is a card that would lie
# if you rendered it today. That is the work list.

Exercise

Run the card-draft script (or its manual equivalent) over your archive tree. Write the three cards with the weakest columns and one paragraph on what the Library view revealed that the folder view hid. Then fix the cheapest gap in one of the three.

Hint

The usual reveal: revisions exist but digests were never recorded, and licenses live only upstream in model cards you did not copy. Both fix in minutes per holding — copy the card, run the shasum.

Where the archive stops being a folder

What a card must answer

Reading your own collection this way

Code

External links

Exercise

Progress

Comments 0