What this registry said, and when
Legal databases publish the law as it is now. A dispute about conduct two years ago needs the law as it was two years ago, and that record cannot be made afterwards. So this one is made as it goes, and published here rather than kept privately.
How to read this
Each time the jurisdiction pages change, every page is hashed and the whole set is sealed into one record. That record carries the fingerprint of the record before it, so nothing can be altered, inserted or removed without breaking every fingerprint that follows. The fingerprint above is the newest link in that chain.
Three separate things can be checked, and they are worth different amounts:
- That the chain is internally consistent. Anyone can verify this from the record alone, with no key and no trust in AI9OS.
- That a record matches the pages it sealed. Each entry stores the SHA-256 of the page body, so the hash can be recomputed from the page itself.
- That a record existed on the date it claims. This is the one a self-issued record cannot establish by itself, and it is why this page exists.
The limit, stated plainly. A record kept only by the party who benefits from it proves nothing about when it was written; nothing stops an issuer producing the whole file in one sitting and back-dating every row. Publishing the fingerprint here does not fix that by itself either. What fixes it is that this page is fetched, dated and retained by parties with no interest in the outcome: search engine caches, the Internet Archive, and the network logs of the service that serves it. The corroboration is somebody else's record, which is the only kind that counts. Where a matter turns on it, a timestamp authority under RFC 3161 is the stronger instrument and should be used instead of relying on this.
What a sealed record claims, and what it does not
It claims this registry SAID this on this date. It does not claim the registry was right. Where an entry was later corrected, both the original and the correction stay in the chain, because a source that shows its corrections is worth more than one that appears never to have made any.
The chain
| Sealed | Jurisdictions | Root | Note |
|---|---|---|---|
| 2026-10-13 | 10 | 76d6f5e7d9763df7179a7b223c2aa9eec3a25b04dcf3b7118d9c21e15c860c0c | 13 Oct 2026: HK, JP, KR official source links; South Korea Article 40 read in the 2017, 2020 and current Korean text, effective date corrected to 5 August 2020; menu and footer changes on every page |
| 2026-09-10 | 10 | 7ac41198cea2a029886696f5187e43d96a81a0df6ca1595928f03e51a1982530 | |
| 2026-09-07 | 10 | 9f43f90276b045c27ec9c8aa606f21b2ae7ae2680ac3a2dd1b67f326df264783 | First sealed snapshot. Record root covers every field, including the date. |
The chain begins 2026-09-07. There is no sealed record before that date and none can be created, which is stated here rather than left for someone to discover.
To ask what was recorded on a given date, cite the root above and the date. Where a matter requires it, a written statement of the sealed position as at a past date is available through the licensed affiliate named below.