Chivas reinforcements Carrillo and Castañeda fail to deliver in Apertura 2026

Jordan Carrillo and Kevin Castañeda have yet to score or assist in six Chivas matches despite prior success.

TruthFoundry Desk

from the fact record

Stands on 4 placed sources from 2 publishers.

Jordan Carrillo and Kevin Castañeda arrived at Chivas after spending a good semester in Liga MX, but their production has not yet been reflected with the Rebaño Sagrado. ^[1] After the first six rounds of the tournament, neither Jordan Carrillo nor Kevin Castañeda has managed to transfer the quality shown during the previous semester to the Rebaño Sagrado. ^[2] Data between Clausura 2026 and the current Apertura 2026 shows a significant drop in minutes and offensive contributions for Jordan Carrillo and Kevin Castañeda. ^[3] After the first six rounds of the Apertura 2026 tournament, neither Carrillo nor Castañeda has been able to replicate the level shown in the previous semester. ^[4]

What this stands on

Jordan Carrillo and Kevin Castañeda arrived at Chivas after spending a good semester in Liga MX, but their production has not yet been reflected with the Rebaño Sagrado. · Record

After the first six rounds of the tournament, neither Jordan Carrillo nor Kevin Castañeda has managed to transfer the quality shown during the previous semester to the Rebaño Sagrado. · Record

Data between Clausura 2026 and the current Apertura 2026 shows a significant drop in minutes and offensive contributions for Jordan Carrillo and Kevin Castañeda. · Record

After the first six rounds of the Apertura 2026 tournament, neither Carrillo nor Castañeda has been able to replicate the level shown in the previous semester. · El Informador

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 Thursday, September 3, 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-04T06:51Z.

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)31e8f767abf6bbcbc7c6085139251515a3cd2a56fa5c731f0cc43785b4cd434f

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.