TruthFoundry News
Better tools. Better news.
Sunday, October 25, 2026 · UTC
Sports

India defeats Hong Kong by 137 runs in Women's Asia Cup 2026

Smriti Mandhana scored a century as India beat Hong Kong by 137 runs in the Women's Asia Cup 2026.

TruthFoundry News Desk
Share on X
Stands on 7 placed sources from 2 publishers.
India defeated Hong Kong by 137 runs in a Women's Asia Cup 2026 match. [1] India and Pakistan are scheduled to play their final league game of the Women's Asia Cup 2026 in Dubai on Saturday. [2] Hong Kong scored 56 for nine in their innings against India. [3] Smriti Mandhana scored a century to power India to a total of 193 for five. [4] India has already qualified for the semifinals of the tournament. [5] The match was played on September 3, 2026. [6] Fatima Sana is the captain of the Pakistan women's cricket team. [7]
Proof7 sources · 2 publishers
What this stands on
  1. India defeated Hong Kong by 137 runs in a Women's Asia Cup 2026 match. · Deccan Herald
  2. India and Pakistan are scheduled to play their final league game of the Women's Asia Cup 2026 in Dubai on Saturday. · Mid-day
  3. Hong Kong scored 56 for nine in their innings against India. · Deccan Herald
  4. Smriti Mandhana scored a century to power India to a total of 193 for five. · Deccan Herald
  5. India has already qualified for the semifinals of the tournament. · Mid-day
  6. The match was played on September 3, 2026. · Deccan Herald
  7. Fatima Sana is the captain of the Pakistan women's cricket team. · Mid-day
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
Article provenance · 7 sources · v 003The worldThe recordThe writingThe filing

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Saturday, September 5, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world2 publishers reported the events across 2 source articles
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
We could not place any of them by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
The automated line wrote this as TruthFoundry News Desk using a large language model at 2026-09-05T12:29Z.
The prompts, verbatim
System instruction (the grounding rules)


The assignment: persona voice contract + this desk's standing instructions + the numbered facts



4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.


Integrity


Content hash (SHA-256)a76e65a0a2f22eec4e780cfa2594f48d01c44ece1ec89f4758d79fc99897ca78


Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed


Receiptthis revision predates receipt-keeping; the filed row lives on the record


Machine readablethe full proof, JSON


Verify



A signature proves who filed this and that it has not changed since. It never makes a claim true.