The Council's Calls
Everyone in this industry claims capability. Almost nobody keeps score. This page is our scoreboard: calls the council made before the outcome existed, and priors we staked before the room spoke — with the corrections shown at the same brightness as the hits.
How to check us — and what checking actually proves
Every entry links to a sealed record containing the full transcript, the models that spoke, the observed serving providers, the cost to the cent, and a sha-256 seal. You can download the exact sealed bytes and recompute the hash on your own machine — the precise recipe (drop the seal field, canonical JSON, sha-256) is printed on every record page beside its seal, with a copy-pasteable command. A naive hash of the served file will not match; the recipe says why.
- What that proves: the bytes you hold match the number we published — the record has not drifted since sealing.
- What it does not prove: that we could not have re-sealed altered bytes. It is a single-writer seal; we hold the only pen. We say this everywhere, including here, because a scoreboard that overstates its own proof is worth less than no scoreboard.
- The gap that used to be here, now closed: this page said for months that nothing on it was anchored to an independent timestamp, and that the "sealed before the outcome" claim therefore rested on our word. Since 13 August 2026 every record's seal is submitted to four public OpenTimestamps calendar servers, run by people with no relationship to us, which commit the hash to the Bitcoin blockchain. Each record page carries its proofs and the command to check them. Only the hash is sent — never the question, the turns, or who flew it.
- What the anchor proves, exactly: that this hash existed no later than a date we cannot move. Not that the record is right. A confidently wrong record anchors exactly as well as a correct one — the anchor dates a claim, it never blesses it.
- Proven, not merely designed: record rec-c2282760 is confirmed in Bitcoin block 962322, mined 2026-08-13T19:10:13Z. That was verified with the reference OpenTimestamps client — not ours — and the block hash it derived matches what an independent explorer returns for that height. You can repeat it: download the proof from that record's page and run ots upgrade then ots verify. Against your own Bitcoin node it is stronger still, and nothing in our setup can stop or fool you.
- The gaps that remain, since one closing does not tidy the rest: fresh proofs are pending until confirmed in a block, and say so. Records sealed before 13 August 2026 are anchored from that date, not from when they were written — that interval is permanent and is our own doing. And three early records carry seals that cannot be recomputed at all (rec-9caa4719, rec-e2ccc3da, rec-a2c0e788, all sealed before a canonicalization fix); we anchor the stored seal and never a freshly computed substitute, because inventing a hash to anchor would be manufacturing evidence. We would rather publish the gap than paper it.
Calls awaiting reality
Forward calls on public markets, sealed with the market's own price at the moment of sealing. Scored when the outcome resolves — win or lose, the entry stays.
The council's edge was contract construction, not polling: the criteria pay only the first PM sworn in after the election, so caretaker scenarios and later rotation slots — the paths the crowd may be buying — pay nothing. Our pre-registered trading rule required 8 points of absolute edge; this showed 3.6. No position taken, and the rule that blocked it was amended only forward, never backward.
Record: rec-bae8d7c3 · protocol pre-registered before the first call
Priors already scored
Before each deliberation, the commander stakes a written prediction of what the room will find. The council then tries to break it. This is the part most teams would never publish: the commander is corrected more often than confirmed, which is the entire reason the council exists.
| Flight | Staked prior | Verdict | Record |
|---|---|---|---|
| Capitalism as arbitrage | "Life itself is arbitrage" | both corrected | rec-2491998a |
| Virality vector | The AI answer layer as new front page | partially corrected | rec-13289ba9 |
| Track Record selection | Structural qualifier + human curation (0.65) | corrected upward | rec-27624862 |
| DARPA µUHV survey | Cascaded vacuum + structure-as-getter (0.55) | two-thirds dismantled | rec-66c99bd0 |
| µUHV premortem | Unit-to-unit pinhole variance kills it (0.5) | deepened past it | rec-91eedaa8 |
| Lift Challenge recon | Rules decide before aerodynamics (0.8); hybrid wins (0.4) | confirmed / falsified by rule | rec-a2c0e788 |
| Terms globalization | Five-move minimal set (0.7) | largely held | rec-5bc90903 |
| Market call #1 | Council converges near market, no edge (0.6) | half right | rec-bae8d7c3 |
Business calls — pre-registered, awaiting their own clocks
The P9 flip: can a site nobody could index find anyone?
Staked 2026-08-10 by Glazier, before any result. Review date 9 November 2026. Resolver locked in advance: Google Search Console for indexing and organic clicks; the coarse arrival bucket recorded at signup for conversion; a plain-language check for the generative-engine claim.
Context, stated because it is unflattering. Until 10 August 2026 this site served
User-agent: * / Disallow: / — a pre-launch dark switch set at the first build and
never flipped. We spent months wondering why search engines showed nothing while instructing
them, daily, to show nothing. Nine pages also carried noindex, including the front
door. That is now fixed, a sitemap is submitted, link cards exist, and an
llms.txt states our limits for answer engines. This call is what we predict happens
next.
- Indexed within 30 days (by 8 Sep 2026): Search Console reports the front door and at least one brief as indexed. 0.85
- An organic search visitor reaches a sealed record within 90 days: at least one click
from search to any
/record/or/briefs/URL. 0.45 - An organic search visitor claims a seat within 90 days: at least one signup carrying the search arrival bucket. 0.15
- A generative engine cites lucentfire.com in an answer within 90 days — a real citation of a page, not a description inferred from the operator's professional profile. 0.30
I am wrong if the site is still unindexed at 30 days despite a submitted sitemap and an open robots file — which would mean the problem was never the gate and our diagnosis today was wrong. The result I most expect to be wrong about is the ordering: I have predicted search (1, 2) fires before generative citation (4). If 4 lands first, the lesson is that writing for answer engines beats writing for rankings, and we should stop thinking about rankings entirely.
Honest limits on this call. Search Console attribution is imperfect and undercounts. The arrival bucket is coarse by design and cannot see a visitor who searches, leaves, and returns directly a week later — so claim 3 is biased downward and a miss there is weaker evidence than a hit. And we are one operator with no marketing spend; none of this generalizes past a site at our size.
The council's judgment on real founder decisions, published with the falsifier and the review date that will score it. If a call is wrong, this page says so on the date it said it would.
The decoupling verdict: every surviving plan reads identically after deleting the word "turbo" — so the domain contributes zero to viability and all of the variance to the downside. The operative risk for a solo founder is not P(Intuit wins) but P(demand letter) × cost-to-respond ($8–40k): the invoice is the ruin event, not the verdict. The latent will-defect tail — a defect surfacing at probate 10–20 years later, heirs never party to any arbitration clause — is likely uninsurable for a pre-revenue solo.
Falsifier (would flip it): trademark counsel producing evidence of Intuit non-enforcement against Turbo- formatives in the relevant classes, or a carrier quoting a real price on E&O covering latent will defects without UPL exclusions. Condition to advance: three paying law-firm pilots within ~90 days, on a mark the founder owns.
Record: rec-a8812f8a · calibration 0.84 · the council was asked to find the risk disqualifying if it was, and did
We proposed that when independently-trained frontier models split on a claim, that claim fails more often — and that this signal is unavailable to any single model. It was going to be the company's positioning. The council took it apart in three rounds.
What died: our sample-size arithmetic was simply wrong — statistical power lives in the divergent cell, so 80 resolved claims buys roughly 16 informative ones, and 250 may not be enough either (near-total agreement against us, 0.05 contested). The "unavailable to a single model" leg collapsed too: single-model sampling entropy may reproduce most of the signal (0.15 contested — the room thinks the leg is false). And a worse possibility surfaced at 0.6: within divergent cells the outlier model may be more often right, which would invert the product's advice from "distrust the split" into "follow the leader."
What survived: the room handed back two pre-registered experiments that decide it — a dispersion-matched temperature ablation (abandon if single-model entropy comes within ~0.02 AUC) and a logistic regression of error on the split indicator conditioned on the contemporaneous market price (dead if the interval straddles zero) — at n ≈ 500, not 80.
Record: rec-c51b1839 · calibration 0.82 · the operator authored the thesis and asked the council to break it; it did
Every meeting-gated play was killed by its own proposer under the constraint that a stranger must be able to buy without a meeting. The room also pre-registered its failure diagnosis: ~80% that if it fails, the binding constraint is distribution, not analysis quality — a claim this page will score.
Record: rec-69732217
Why publish the misses
Because a scoreboard that only shows wins is advertising, and everyone can tell. The claim we are actually making is narrow and checkable: this council changes its own mind under pressure, and we keep the receipt either way. Three of the records above contain models retracting their own positions mid-deliberation when arithmetic or a rulebook contradicted them. That behavior — not raw capability — is the product.
On being copied
The method here is not secret: convene several frontier models, make them argue, have rival-lab judges harvest the disagreement, seal it, stake predictions in advance, and publish the score. Anyone may run it, and the industry would be better if more did. What cannot be copied is an accumulated public record — a track record can only be started, and it takes exactly as long to build as it took. The machinery is documented in the Pilot's Manual and the flight log.