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.
- Fashion Resorts — this register
- 2026-10-29 · 722fb8b2700fec6f · published
Hashed from content: records, texts and configuration. Machine-readable at /revision.json. - Luxury Hospitality Library
- 2026-09-13 · 8309a99d29f72273 · received 2026-09-17
register-min held here as the file received on 17.09.2026. The file's own header declares version 2026-09-13 and revision 8309a99d29f72273; the file name and the project README declare 2026-09-17 and cae82eef1097b252. The pair recorded here is the one inside the file, per HOUSE-RULING-17 §1. This register cited HOUSE-RULING-08 §5 here from 17.09 to 06.10; ruling 08 is document 31 and its §5 is about a count stated in prose carrying the revision it was read from. The rule applied here is ruling 17 §1 (document 44): the pair is read from inside the file, the file name is not a declaration. Corrected 06.10.2026 by this register's own citation check. data/people.json and data/brands.json are carried from it verbatim, keyed by Library code; no brand on a record is joined to a code by name. - ↳ earlier
- 2026-09-11 · 89bfbc8a6eca7567 · named in the dispatch of 11.09; file not enclosed
- ↳ earlier
- 2026-09-13 · 8309a99d29f72273 · named in kit v1.2 sources.json; file not received here
- ↳ earlier
- 2026-09-17 · cae82eef1097b252 · declared by file name and project README; not the pair inside the file
- House property key (PRP)
- 2026-10-01 · 5bbe12dd054ba96b · in force
All six files of HOUSE→LHL-F-003 and all three of 004 verified by their own sha256 before anything here changed. Every record in this register now carries a key: 240 of 240. - House master registry
- 2026-09-11 · — · in force
Overlaps in also_in and the tier column come from the master registry v15. Its Fashion membership column predates HOUSE-RULING-04 and v15's own exclusions: 94 rows differ from this register, listed in export/LHL-F-prp-membership-drift.csv.
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.