20 claims are tracked: 20 by the desk. Here is the rule they were held to, who decides, what we have to declare, and the claims we turned down.
Every claim in the Ledger was chosen by one person, and for the first 20 of them the reason was not written down at the time. The choice of what to track is where bias would hide. This page cannot remove it. It states the rule, makes the choice visible from now on, and says what is still missing. The policy took effect on 19 October 2026.
A proposal does not publish anything. The desk decides whether to accept it, and writes the headline, the resolution criteria and the sources it will consult. The Ledger’s submission form is on the Ledger page.
| A claim is tracked only if… | How we know |
|---|---|
| A named party said it: a company, agency or named person, in a source we can link and quote word for word. | Checked by a script. Holds for 20 of 20 claims. |
| The statement has a date, and an independent archive copy of the source exists, so it cannot be quietly reworded. | Checked by a script. Holds for 20 of 20 claims. |
| It names an outcome and a deadline, and the deadline falls after the statement. | Checked by a script. Holds for 20 of 20 claims, but 2 of those do not meet it as the claimant stated it (see below). |
| We can write the resolution criteria and name the sources that will settle it, before the deadline. | Checked by a script. Holds for 20 of 20 claims. |
| Someone with the public record, and no private information, could settle it. If only our opinion can settle it, it is not tracked. | A judgement the editor makes. A script cannot check it. |
| It is about a capability, a schedule or a commitment. Never about a person's honesty, and never one of our own forecasts. | A judgement the editor makes. A script cannot check it. |
| Nobody paid for it to be tracked, and nobody paid to keep it out. | A judgement the editor makes. A script cannot check it. |
A claim must also be accepted before its deadline. A claim logged after its deadline has passed cannot have criteria fixed before the outcome could be known, and 2 of the 20 here were logged that way. The policy does not allow any more.
The editor decides whether a claim is accepted. There is one editor, and no outside panel decides this today.
That is a weakness, and the page says so: nobody outside can yet check the choice of what was tracked and what was passed over. The rejected-claims log below exists to make that choice visible, and outside reviewers will be shown by name on the reviewers page when there are any.
Accepting a claim is a separate decision from scoring it. The Ledger's rule that the person who captures a claim does not write its verdict is on How we check.
SymbiQ is written and kept by one person, with no money or ties to any company whose claims turn up on these pages (About, Funding). Nobody has paid for a claim to be tracked, for a verdict, or for the wording of either.
No separate declaration of shareholdings, past employment or consulting has been filed. Until one is, read the statement above as the editor's word and the absence of a filed declaration as unknown, not as none.
If the editor turns out to have an interest in a claimant, claims of theirs are still tracked, and the interest is declared on each of those claims' pages, beside the claim and beside its verdict.
The claimants named in the Ledger today are: Atom Computing, D-Wave Quantum Inc., Executive Order 14412 (The White House), Fujitsu and RIKEN, Google, IBM, IonQ, Microsoft, NIS Cooperation Group (EU), NIST, NVIDIA, Pasqal, PsiQuantum, QuEra Computing, QuNorth, Quantinuum, Rigetti Computing.
A Ledger of only next-year claims would be easy to score and would say little. A Ledger of only distant ones would score nothing for years. Each claim is placed by how far its deadline was from the day it was accepted.
| Deadline | Claims | Share | Target | |
|---|---|---|---|---|
| Already past its deadline when logged | 2 | 10% | 0–10% | within target |
| Near term: due within 24 months | 12 | 60% | 50–75% | within target |
| Medium term: 24 to 60 months | 4 | 20% | 15–35% | within target |
| Long tail: more than 60 months | 2 | 10% | 5–20% | within target |
The targets were set on 19 October 2026 by someone who had already seen the current mix, so they describe what the Ledger is meant to look like, not a plan the first 20 claims were chosen to meet. New claims are not accepted after their deadline.
None yet. The log began on 19 October 2026 and no proposal has been declined since. That is not evidence that every proposal was accepted: it may mean none has arrived, and the desk has no way of showing you which.
When a proposal is declined, an entry is added with one of these reasons. The submitter is never named.
This log starts on 19 October 2026. We have no record of claims that were considered and passed over before then, so it cannot show you what the first 20 claims were chosen from.
This is version 1, in force from 19 October 2026. A change is made in the policy file, and this page shows the date it took effect. A change that affects how an existing claim is scored goes on the corrections log.