Accuracy per release
Each release of alalanet signs a release statement (kind 4327) into the public transparency log when it starts. The statement names the build and the log index from which the entries are that build's. Below, for each release, the signed verdicts between it and the next release, counted by decision. Anyone can count them again from the log. A release's record holds figures from our own checks before the release; those cannot be recomputed outside.
Recomputed every 10 minutes. JSON: GET /v1/accuracy.
Build 2bc3ea98 (still serving)
Release statement signed 2026-11-20T00:00:42Z (statement, log index 1130887). MCP server 1.5.4, Trust Score revision v1.15. Log entries from index 1130887 on.
| Signed verdicts | All | allow | hold | block | other | Targets judged before too | Decision changed |
|---|---|---|---|---|---|---|---|
| pre-payment decision (4303) | 0 | 0 | 0 | 0 | 0 | not compared | — |
| install verdict (4310) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| repository verdict (4315) | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
This release carried no accuracy record.
How the verdicts are counted
Verdicts are the signed statements of kinds 4303 (pre-payment decision), 4310 (install verdict) and 4315 (repository verdict) in the public log, counted by decision and by reason code (a reason's text before its first colon), from a release's from_log_index up to the next release's. An answer that reused a recent verdict signed nothing new, and an answer that signs nothing (a private check) is not in the log: neither is counted. The same statement signed twice within one second is one event, and counts once. Releases before the first release statement are not listed: the log does not say which build signed what before it.
Changed decisions
Install and repository verdicts only. A target (the statement's d tag) judged in a release's window and also before it is compared: its first verdict in the window against its last verdict before the window. A changed decision can come from the release's rules or from the target itself; the count does not say which. Pre-payment decisions are not compared: each judges one payment's terms.
Reported figures
A release's record holds figures from alalanet's own checks before the release: mutation runs on the changed rules (mutants killed of those made) and comparison corpora (answers that differ between the build before and the build after). They are reported, not recomputable from public data: the service's code is not public. The release statement signs the record's sha256.
Not shown
This page does not show false holds and blocks, or complaints.
Verify
Read the release statements (kind 4327) from the log. For each, count the entries of kinds 4303, 4310 and 4315 whose log index is at or after its from_log_index and below the next release's from_log_index; count each event id once, at its first entry. Check each statement's Nostr signature against alalanet's server key and its inclusion proof (GET /v1/attestations/{id}, or alalanetd verify). sha256 of the bytes of GET /v1/accuracy/records/{n} equals the release statement's record_sha256.