Product
Evidence Register
Claims about the platform graded by what settled them, recorded append-only, with each verification run kept.
On this page
What it does
The Evidence Register records the claims RJV makes about its own platform, grades each by what settled it, and keeps the history. Claims are append-only: a claim is never edited, it is superseded by a new claim, and every verification run, passing or failing, is a row of its own.
What exists now
| Capability | What it does | Where |
|---|---|---|
| Public register | Lists the active claims, filtered by evidence class and by what settled them, with the verified head of the audit chain. | Evidence and limitations |
| Recording a claim | Authorised staff record a claim against a subject with an evidence class (for example measured, reproducible, attested or asserted). A claim is recorded without a verification tier. The tier, which says what settled it, is added only when the verification harness records the verification: the runtime holds no write on the verification log, so no claim recorded here can name a method that nobody has run. | POST /evidence/assertions, staff with a second factor |
| Superseding a claim | A new claim names the claim it replaces and must concern the same subject. The earlier claim stays in the record and leaves the public list once its successor takes effect. | POST /evidence/assertions |
What a grade establishes
A grade states how a claim was settled. It does not make the claim true, and a digest or a log row is not a proof. A claim with no recorded method shows that it has none.
Operating needs
- PostgreSQL; the tables refuse updates and deletes.
- A staff account with the evidence grant and a second factor.
Limits
- Verification runs are recorded by the verification harness, not through this register, so a newly recorded claim shows that it has no recorded method until one is run.
- The register holds claims about RJV's own platform; it is not a general fact-checking or document store.
Availability
The Evidence Register is running on RJV's own platform. RJV does not sell a licence for it as a separate product today: the commercial terms state what is on sale. It can be part of the result of an engineering engagement, where the written proposal names it, its licence terms and what you would hold at the end. To discuss it, use Work with Us.
Evidence
The staff operations, the append-only guard and the superseding rule are covered by the platform's own tests. The register itself is the public record of what has been graded.
Works with
- Audit Chain: Requires. Each recorded claim and verification is entered in the chain.
- Identity and Access: Requires. Staff recording a claim must hold the grant and a second factor.
- Document Vault: Works with. Claims about the platform are recorded there; custody of an account's own documents is here.
- Publishing and Discovery: Works with. Claims appear on the public research pages.
Where it runs
| Supported target | A customer-controlled Linux host on x86-64 with PostgreSQL 18 (linux-x86_64-customer-controlled). |
|---|---|
| Not yet supported | Windows, macOS, phones and tablets, and Linux on other architectures. Each needs its own installation, update and recovery evidence before it is supported. |
| Check a device | Run rjv2 preflight on it. It reads the operating system, architecture, memory, disk, listen address, configuration, database, database role and schema, changes nothing, and exits non-zero if release 2.0.0-alpha.1 cannot run there. |
| Installed as | One application and a PostgreSQL database. Installing release 2.0.0-alpha.1 (schema 100) installs every system on this site, including Evidence Register. |
| Data | It stays in the PostgreSQL database you run. The only outside service the release can use is an outbound mail relay that you configure. |
| Updating | A release is a numbered build. The schema is applied by a separate owner step (rjv2 migrate), and the application refuses to serve a schema it was not built for. |
| Backup and restore | rjv2 backup writes a checksummed dump. rjv2 restore restores it into an empty database and checks the checksum, the schema version and the audit chain of every account. |
| Leaving | The data is in your own database and can be dumped at any time. What you may do with the release is set by the terms on deployment and ownership. |
- Published
- 29 October 2026
- Revision
- 5