Sources and revisions
What this build is compiled against, named by version and revision rather than by date.
What this register cannot tell you about its own past. It keeps every version and revision pair it has published, and from this build onward the list of records that changed at each one. It does not keep the content of past revisions. So a question of the form how long did a wrong figure stand here can be answered in revisions and dates, and a question of the form what did this card say three revisions ago cannot be answered at all. That is stated rather than left to be discovered.
This register publishes its own pair as well as reading everyone else's. We asked the Library for a version and revision four times in a week while shipping our own data — the search index, the exports, the archives — with no revision at all, which left a partner unable to tell whether anything of substance had moved. /revision.json is the machine-readable form.
A revision can change inside a single day, so a date is not an identifier. Every shared register the collection reads is recorded here as a version and revision pair, and a rebuild that changes one of them changes this page with it.
- Luxury Resorts — this register
- 2026-10-06 · 6ce32ed34ccddd83 · published
Hashed from content: records, texts and configuration. Machine-readable at /revision.json. - Luxury Hospitality Library
- — · — · not yet received
register-min.json has not been read by this collection. data/people.json and data/brands.json are empty; no person or brand code is claimed, and origin carries text without pretending to be a link. - House property key (PRP)
- 2026-10-05 · e17cc8cf3c80b042 (rev28) · received 2026-10-06
rev28 supersedes rev27, which this register never read. Every published record now holds a key; seven class-3 duplicate pairs were merged here on 06.10 and their key pairs await the House. - House master registry
- v41 · — · received 2026-10-06
Carries the three withdrawals of 18.09 as REMOVED → Fashion, and the Beaver Creek merge with LHL-D carried onto the surviving key.
Joining
Records are joined to people, brands and sister collections by code, never by name. Where a code has not yet descended, the link is left empty rather than guessed — a register that joins on a string joins the wrong subjects silently.