backpacks
An aggregator and exploration tool for technical and boutique carry — makers, packs, and lines, with every spec traced to its source.
backpacks catalogs technical and boutique carry: backpacks, and the slings, pouches and organizers that travel with them. Every specification here is tied to the page it was read on.
The design principle is signal > canon. Specs get copied between retailers, reviews and forums until nobody knows who measured what. So this dataset records signals — one claim, one source — and resolves them into records that keep the disagreements visible. Where a maker’s own page contradicts itself, both readings stay.
Two things this dataset will not do. It will not publish a number without a source: what we don’t know is written down as a gap, on the record, where an empty field would otherwise read as an answer. And it will not pretend to an authority it hasn’t earned — the people who know this subject best are the makers, and the community that has documented them for years.
- Packs: every tracked pack, by maker, capacity, carry style and use case
- Makers: who builds them, including the lineages and the acquisitions
- Data: the raw YAML, the schemas, the licence, the provenance
- Cite this: stable ids and citation formats
No scheduled fetcher touches any source here. Every source in the registry is
marked manual: two of these makers ask in their terms that their sites not be
crawled, one asks that its materials not be copied, and the community
publications are not ours to harvest whatever their robots.txt permits.
The founding corpus itself was gathered by an AI agent, fetching each cited page once, on request — not by a person, and not by a crawler. Saying so plainly costs us the nicer sentence and is the only version worth publishing. How the data was collected sets out the method, and the one question it leaves open.
This is a Bussetech Software Studio project. Its data lives in the repo as text and the site is rebuilt from it on every change.