Nuño Sempere called it:
“Our forecasters’ 90% confidence interval for the largest number of deaths (civilian and/or military) that Russia will inflict in a NATO country in a single incident before August 15, 2027 is 0 to 20, with the 50th percentile- falling between zero and one deaths.”
We find out by Aug 15, 2027. 359 days to go
Nuño Sempere: “Our forecasters’ 90% confidence interval for the largest number of deaths (civilian and/or military) that Russia will inflict in a NATO country in a single incident before August 15, 2027 is 0 to 20, with the 50th percentile- falling between zero and one deaths.”
MET if The largest number of deaths (civilian and/or military) inflicted by Russia in a single incident on the territory of a NATO member country between August 17, 2026 and August 15, 2027 on the deadline date, before 2027-08-15 23:59 (UTC).
Settles by documented review of public evidence against these locked criteria; the reviewer is named and the reasoning published.
The original wording did not settle the timing on its own. The reading above was chosen at registration and locked with the claim — it was not decided after the fact.
Test details
Resolves YES if, over the period from August 17, 2026 through August 15, 2027, no single incident attributed to Russia in a NATO member country causes more than 20 deaths (civilian and/or military combined), as reported by official government sources of the affected NATO state.
Quote verified against the source
Added by Thonest from a public source. The person quoted did not submit, approve, or endorse this record; the wording is verified against the source itself.
Read the original on blog.sentinel-team.org ↗
Weekly Sentinel global risk brief, Europe section, following reports of a thwarted Russian assassination plot in Warsaw and drone incursions into NATO states.
History — append-only
Proof
2 hashes from this record to the anchored root
- 0x130e1780de7fa407f146f9ecb26b8314a4cabd6dcafeea9f60df4fd11f81346d
- 0x9bef164e06afc054a1dcf7db01ff1468e22bc4588795d20eb9eeb5bb480c967e
batch #66 manifest · 4 entries
the contract refuses any batch that doesn’t follow the previous one, and has no function to edit or delete one — including for us
0x532fbdc4…38853d on block explorer
No independent copy could be captured for this source.
view the canonical capture · the page as served to us, kept verbatim and covered by the evidence hash
✓ The anchored proof cannot be rewritten, and the published record is append-only by default. Everything that happened afterward is in the history above — corrections are appended, never silently edited in.
The check runs in your browser and reads the anchored root straight from a public Base node — not from Thonest. How this works.
Disputes
No disputes have been filed. If something here is wrong — a misquote, a wrong date, a misattributed source — say so and it gets answered on the record. How disputes work.
Related