Publisher: hrl-han, the research network of Hapax Research Lab.
Legal entity (as filed): Hapax Research LLC, organized in Wyoming on 2026-05-10, filing ID 2026-001973400.
Contact: hrl-han@hapaxresearch.com.
What this record is. It describes how this edition of the site was produced and checked, so that any reader can check that account. The records the site links, and the sources they cite, not this record, are the evidence for what the site says.
Edition: Edition 1.
The edition is bound to the SHA-256 digest of its file manifest. That digest is not stated on the edition itself, since a set of files cannot state its own digest. Anyone can recompute it: list every published file as path<TAB>sha256 (the path relative to the site root, the SHA-256 in lowercase hex), in bytewise path order, each line ending in a newline, and take the SHA-256 of that list. The value is kept in the release receipt.
1. How the edition was drafted
| stage | date (2026) | drafted by | identity basis |
|---|---|---|---|
| site source, records and first copy | September 24 | OpenAI GPT-6-astra | identified from the service’s session record, which the lab keeps and does not publish |
| release edits (naming, contact, labels, correction path, this record’s page) | September 25 | Anthropic Claude Opus 5.5 | identified from the service’s session record, which the lab keeps and does not publish |
| earlier wording carried into the copy | September 22–23 | Most of the copy (141 of 159 traced sentences) was written with the site source by OpenAI GPT-6-astra. Two sentences came from research drafts produced with OpenAI GPT-5.6. Four contact and governance sentences come from the lab’s sender rules, drafted by Anthropic Claude Opus 5.5. The phrase “a functional R&D laboratory” comes from a ruling by the lab’s principal on how the lab is described. For the remaining sentences, the drafting model is not established from a record. | per sentence, as stated; “not established” where no record names a model |
2. How the edition was reviewed
Each reviewer was given one named hostile role and the finished site only: no drafting notes and no other reviewer’s findings. Reviewers came from developers other than those of the drafting models (OpenAI, Anthropic). Reviews are model outputs, not human reviews.
| role | reviewer (developer) | web access | outcome |
|---|---|---|---|
| hostile journalist | A review in this role by xAI Grok was planned but did not run for this edition; the final pass took this role. | — | — |
| skeptical methods expert | Moonshot AI Kimi (model version not established from a record) | yes: it opened each record’s cited source and noted when; three sources could not be read (one returned an error, one was a binary file, one a form-gated registry), and it recorded those as not checked | six findings. One critical (the review record was still unfilled; fixed by filling it). Two major: one led to publishing the release rule on this page, and one was rejected because the file it reported missing is present. Three minor, all fixed: a source’s own hedge restored through a published correction, the probability-precision caveat added, and forecast P4’s statutory start date stated |
| opposing counsel or regulator | Meta Muse (Muse Code 1.3.0) | yes: every one of the 19 sources it says it opened appears in its own fetch record; it listed the lab’s two omg.lol pages as not fetched, and the Wyoming business search as form-gated and not checked | eleven findings. Seven led to changes: licence scope stated for third-party sources, forecast P3’s unbound resolver disclosed, P4’s date conversion shown, a caution against sending personal data, the model-identity basis stated, one naming sentence, and the most damaging sentence reframed. One of those also became the provisional withdrawal-and-retention wording, which the lab’s principal adopted. One was rejected (an image it reported missing is present). One described this record’s pre-release blanks, now filled. Two were carried into the question of whether draft forecasts appear (decided: they appear, fenced as drafts) |
| defect finder | Qwen3.8-flash-next (Alibaba; run on the lab’s own hardware) | no | on an earlier build: its output degenerated after about 25 findings. Of those 25, 7 led to changes, 10 were rejected with reasons, 2 concerned the review record’s pre-release blanks, 2 needed no change, and 4 were carried to other reviewers |
| final “most damaging sentence” pass | Published only after a final pass on these exact files, by a developer whose model had not reviewed this edition, raised nothing the review had not already decided. For this edition, the last such pass was made without web access, on the text of the files. That pass’s record is kept with the release receipt. | ||
How findings were decided. Each finding was checked against the site’s files and its cited sources. It was then accepted and fixed, rejected with the reason recorded, or set outside this edition with the reason recorded. Findings were not decided by counting how many reviewers agreed. Across the three reviews completed before the final pass, 42 findings were considered: 18 led to changes, 4 concerned this record’s pre-release blanks and were resolved by filling it, 12 were rejected with recorded reasons, 2 needed no change, and 6 were carried to another reviewer’s question or to a decision recorded here (whether draft forecasts appear: they appear, fenced as drafts). One change became the two sentences on withdrawal and retention that the lab’s principal adopted. The code that decides which files may be published was reviewed separately. Two high-severity findings were resolved before release: these blanks, by this filling; and hidden files, which the upload step would have dropped although the check counted them, are now refused. A first final pass found one damaging sentence: the staffing statement did not say, where it was made, that the lab has a human principal. It was rewritten. A second final pass raised five items: four repeated findings this review had already decided, and one new minor item, that the forecast protocol’s note on its inherited citations is written in internal terms, which is carried to the next edition. Because this paragraph then changed, a further final pass read the text of these exact files. The review stopped when every critical and major finding had been fixed, rejected with a recorded reason or set outside this edition with a recorded reason, and a final pass on these exact files raised nothing the review had not already decided.
3. How publication was authorized
One such request was found: the lab’s principal was asked to adopt, and on 25 September 2026 adopted provisionally, the two sentences on withdrawal and retention of messages in §4, because they commit the legal entity. No request to approve any other wording of this edition, and no other approval, was found in hrl-han’s publishing, review and coordination records when this edition was prepared for publication. hrl-han publishes an edition once its checking is complete, under a standing rule that hrl-han’s principal, who is not named here, adopted on 24 September 2026.
The release rule. On 24 September 2026, hrl-han’s principal, who is not named here, gave standing authority to publish this site’s editions without a further personal approval, provided each edition first passes the applicable checks: rights, privacy and consent, the exact files released, independent review, and the hosting and publishing path, with the published result read back afterwards. For this edition those checks were:
- hostile-reader reviews by models from developers other than those of the drafting models;
- every critical and major finding fixed, rejected with a recorded reason, or set outside the edition with a recorded reason;
- an independent review of the code that decides which files may be published;
- a final pass on the exact files by a developer whose model had not reviewed the edition;
- a release bound to the SHA-256 digest of the edition’s file manifest, which the publishing system enforces;
- a search of the publishing, review and coordination records for any request to a person to approve the final wording.
The release is bound to the exact manifest digest described at the top of this record. A changed file changes the digest, so the authorization no longer applies to it. What stands behind the edition is this record, the procedure that released it, the network’s duty to correct it, and the legal entity’s answerability in law. That is not the same as there being no person behind the lab, and this record does not say so.
4. Corrections
Corrections are received at hrl-han@hapaxresearch.com. The network commits to receipt, retention and published correction. It promises no response time. A sender may withdraw a message at the same address and it will be deleted from the store, unless it is already quoted in a published correction with the sender’s permission. Messages are kept until the correction they propose is resolved. This handling is provisional. A receipted process, in which each message is given a reference its sender keeps and can cite, is planned; no date is set. A correction is published as a new, dated revision beside the original wording, which stays readable. Published corrections · How to propose one