Taking the temperature of AI.
Microsoft Confirms Copilot 'Super App' Coming This Year
Sources cited
What we drew from, unmediated.Corroboration
Independent outlets carrying this claim, and who reported it first.This story currently appears at a single reported origin. That is disclosed here plainly, not treated as a fake-news signal on its own -- a genuine scoop looks the same as an unconfirmed claim until other reporting catches up.
This receipt does not show a percentage confidence score. Independent-origin count, editor votes and model fact-checks below are real counts, but no calibrated mapping from any of them to an actual probability of truth exists on this newsroom yet -- showing one would be fabricated precision, not evidence.
Who wrote it
No production record.This story predates the newsroom's real model-per-journalist pipeline. It carries a byline in the archive but no per-model draft or editor-consensus record exists for it, so none is shown here rather than one being invented.
Verification gate
Did every load-bearing claim survive a check against its cited source?This story was never run through the verifiability gate (scripts/newsroom/gate.mjs). Its claims have not been checked against its cited source by our pipeline. That is a gap, not a pass, and it is shown as one.
Source fetch & independent fact-check
Was the cited URL fetched and confirmed to exist, and did separate AI models -- not the ones who wrote the draft -- independently confirm the central claim against that live page?- Source URL fetched
- yes, HTTP 200, 2026-07-31T22:53:28.299Z
- Fetched page content hash
- 679248601dc7d0ee2a22ce09ca2f2203b97ae3f924e78978cf44ff93f1235009
The headline of the source text directly states, "Microsoft confirms Copilot ‘super app’ coming this year".
The source text's headline and body directly state that Microsoft's CEO confirmed the Copilot super app is coming this year.
- Threshold to pass
- Unanimous: every checker must independently return YES. A single NO, ERROR, or unparseable answer fails the whole check (fail-closed), not a majority vote.
- How this panel was chosen
- Fixed checker pair (not yet TVRF-selected). The blueprint calls for the panel to be chosen by a public-randomness round (TVRF/drand) AFTER the claim and sources are sealed, so no one could have picked favourable checkers in advance. That selection step does not exist in this build yet; the same two checkers run every time.
Per this project's own DAE rule, only container-pinned, bit-reproducible ("DAE-satisfying") model runs may cast a BINDING vote; models reached through a closed API may only participate as witness testimony. Both checkers here run as closed OpenRouter API calls, not DAE-pinned local containers, so under that rule neither vote is binding yet. In practice they are still the only check that runs: an article is refused unless both agree. This pipeline currently treats witness testimony as if it decided publication, which is a real gap against the stated law, not a decorative one.
Cryptographic record
VeriStamp certificate and the VeriBOX publish event.No VeriStamp certificate and no VeriBOX tape event exist for this story. Nothing here claims otherwise.