Nothing
There is no analytics package, no tag manager, no pixel, no beacon, no A/B framework and no error-reporting service. No cookies are set and no browser storage is written. Nothing on any page identifies a visitor, and nothing is transmitted anywhere as a result of a visit beyond the requests your browser makes for the page itself.
The site is served as static files. Whoever hosts those files will see ordinary web-server request logs — that is a property of the hosting, not a data collection this site performs, and this site adds nothing to it.
There are none
Every stylesheet, script, image, font stack and data file loads from this origin. There are no remote fonts, no content-delivery networks, no embedded video, no social widgets and no external scripts of any kind. Typography uses the system serif, sans and mono stacks declared in the canonical stylesheet, so no font request leaves your machine.
The only outbound links on this site are ordinary navigational links to nightwatch.hermanity.dev and hermanity.dev. They are followed only if you click them.
What js/site.js does
One first-party script ships with this site. It adds a verdict filter to the experiment ledger and marks the current navigation entry. It makes no network requests, reads no storage, sets no cookies and observes no user behaviour.
Every measurement, verdict and conclusion on this site is present in the served HTML. With scripting disabled the ledger reads in full, in order, with all of its numbers — the filter controls simply never appear.
What the published record contains
This site publishes research artifacts about a dispatch policy: dataset shapes, metrics, gate results, artifact paths and digests. It deliberately does not publish:
- Prompt bodies or any training or evaluation row content.
- Raw model completions, which exist only in mode-0600 private artifacts.
- Session content, conversation transcripts or audit transcript bodies.
- User identifiers, account names, email addresses or personal data of any kind.
- Credentials, tokens, keys, hostnames or internal network addresses.
- Digests of private artifacts, which are retained in the private receipts instead.
Provider names that appear throughout the record — Claude, Grok, Kimi, MiniMax, Z.ai — are the routing classes of the dispatch policy being studied. They are labels in a five-class classification problem, not accounts, and no usage attributable to any person is published.
Where a measurement was never taken, no number is shown and the absence is stated. Nothing on this site is estimated to fill a gap.
If something here is wrong
Corrections are handled the same way the research record is: the record is changed first, and the change is published rather than quietly applied. This programme's own history includes a published falsification of its own headline result, which stands on the ledger beside everything that came after it.
Reach the wider project through hermanity.dev. No personal contact address is published on this site by design.