Folarin Balogun omitted from Monaco Conference League squad after Everton transfer collapse

Monaco omitted U.S. striker Folarin Balogun from Conference League squad and PSG trip after Everton transfer collapsed.

TruthFoundry News Desk

Stands on 4 placed sources from 2 publishers.

Monaco left U.S. striker Folarin Balogun out of its squad for the Conference League and the team's trip to Paris Saint-Germain after his proposed transfer to Everton collapsed. ^[1] Monaco sporting director Thiago Scuro said on 2026-09-04 that U.S. striker Folarin Balogun pulled out of a proposed transfer to Everton because he felt uncomfortable that the English club raised doubts about his health in a medical examination. ^[2] Monaco begins the Conference League league phase on 2026-10-15, and Folarin Balogun's name did not appear on the club's squad list published by UEFA on 2026-09-03. ^[3] Folarin Balogun will miss Monaco's match at Paris Saint-Germain on 2026-09-04 after being omitted from the travelling group. ^[4]

What this stands on

Monaco left U.S. striker Folarin Balogun out of its squad for the Conference League and the team's trip to Paris Saint-Germain after his proposed transfer to Everton collapsed. · Winnipeg Free Press

Monaco sporting director Thiago Scuro said on 2026-09-04 that U.S. striker Folarin Balogun pulled out of a proposed transfer to Everton because he felt uncomfortable that the English club raised doubts about his health in a medical examination. · ESPN

Monaco begins the Conference League league phase on 2026-10-15, and Folarin Balogun's name did not appear on the club's squad list published by UEFA on 2026-09-03. · Winnipeg Free Press

Folarin Balogun will miss Monaco's match at Paris Saint-Germain on 2026-09-04 after being omitted from the travelling group. · ESPN

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 · 4 sources · v 001worldrecordwritingfiling

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Friday, September 4, 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

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.

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-04T12:32Z.

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)6b44d14d4f4a69dbd2f21b67b562e9863dc0ee9c5076d2eec361dc07ab0b5f5e

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.