(U//OS) · The Prescient Desk · Register

Conformance Register

Every party that has made a conformance statement against these standards, the level claimed, who assessed it, and what the verifier said. A standard with one conformer is a house rule. This page exists so that fact stays visible rather than implied.

What listing is not. Appearing here is not an endorsement, a certification, or an assessment of anyone's forecasting ability. Conformance certifies process only — that a record was sealed before its outcome, that misses are present, that the count is committed. It certifies nothing about the quality of what was predicted. That is RPAS 1.06, LIAS 1.05 and KNM 1.07, and it is the whole reason this register can exist without becoming a credentialing machine.

Register

PartyStandardStatementAssessed by ScopeVerifiedRecord
loading…

How to be listed

  1. Seal your forecasts locally. Nothing is submitted here and nothing is stored here. A scheme in which a server receives, stores, or could edit predictions is not an implementation of this method (KNM 1.05), so this register holds no vault and accepts no submission (KNP 1.02).
  2. Publish your own hashlog at a URL you control, with an append-only mechanism you do not solely control — a public repository history, a timestamp authority, a chain anchor (KNP 4.03).
  3. Run the verifier against it: python knp_verify.py <your hashlog URL> --json
  4. Send the URL and the verifier's JSON output. Nothing else is needed and nothing else is wanted.
  5. The entry lands with whatever the verifier said, unedited, including the should-departures. A modified statement is a normal outcome and is listed as such (KNM 2.03).

The verifier is standard-library Python, knows nothing about any particular committer, and is published here: knp_verify.py. Run --selftest for the interoperability vectors if you are implementing in another language.