How we did it

• Plataforma de Contratación del Sector Público (Spain's official public procurement platform, contrataciondelestado.es)^{source 2}. It is governed by Law 9/2017 on Public Sector Contracts: contracting authorities publish their buyer profile on it, and the autonomous communities may have a platform of their own^{source 3}. The buyer profile exists to ensure transparency and public access to the activity of each contracting authority^{source 4}.
• Open data from the Platform, on the Ministry of Finance website. It is generated by the Directorate-General for State Assets from what the contracting authorities themselves enter^{source 5}. We use three datasets: tenders published on buyer profiles, tenders that arrive by aggregation from other platforms (since 1 January 2016) and minor contracts (since 1 January 2018)^{source 6}. The aggregated ones are those from the regional platforms^{source 7}. The file format is set out in the official syndication specification^{source 8}.
• Register of mayors and councillors of the Ministry of Territorial Policy and Democratic Memory, in its Local Information System^{source 9}, and the search service for local elected representatives on Red SARA, the Spanish administrations' communications network^{source 10}. We use them only to find out the party recorded for the mayor of each council on each date.
• Boletín Oficial del Estado, Spain's Official State Gazette, for the text of Law 9/2017^{source 11} and of the previous law^{source 12}.

• Download robots, which fetch notices and tender specifications from the public platforms^{source 13,source 14}.
• Our own Python programs, which turn the official files into tables, with one row per contract award result^{source 15}.
• A version-controlled repository, in which every change is recorded with its author and date^{source 16}, as entered by whoever makes it.
• SHA-256 hash manifests (see below).

We have let them read, organise, code, suggest wording^{source 17} and review, but not decide. This is what we told Antigravity: You are not a lawyer, you do not decide litigation strategy, you do not sign. (our translation)^{source 18} Some of the ones we have used:

• Manus, since 1 January 2026^{source 19}: prepared the first analysis documentation for the repository^{source 20}.
• The Clone, Miguel Ángel Domínguez's digital brain, since 17 April 2026: received the investigation archive to organise what we knew^{source 21,source 22}.
• Antigravity, from Google^{source 23}, since 21 May 2026: received the case to integrate it into the digital brain^{source 24,source 25}.
• Claude Code, from Anthropic^{source 26}, since 2 July 2026^{source 27}: programmed the analysis of the open data^{source 28} and checked that every tender and every person mentioned in the complaint is linked to a document in the investigation file^{source 29}.

A SHA-256 hash is a string of letters and numbers calculated from the contents of a file. If a single bit of the file changes, the hash is different^{source 30}. That is why it can be used to show that a file has not changed.

We have generated three manifests of the investigation file, each with the hash of every file it covers. Here we publish the hash of each manifest: if any of them is produced later, anyone can check whether it is the same one, because a single change would make the hash stop matching. We publish this page ourselves: a hash shows that a manifest has not changed, but not how long it has existed.

• 2 July 2026^{source 31} · db2cb7498216d7d7994a465ca93ae50f77641b013e008d97f0ca8fb9544f660a^{source 32}
• 4 July 2026^{source 33} · d8159666f9845f2d4569fe0f7fd1f7edc5ba304395bd3be2bfb20f5d35a2238d^{source 34}
• 22 July 2026^{source 35} · e3e071e13c41cfe262226bdb3d9939625712c6c2ef50adf19e9fd1a15ff96c5e^{source 36}

Before filing the criminal complaint, we will regenerate the manifest from the final version of the investigation file^{source 37}.

How to check the hash of a file^{source 38}:

• macOS or Linux: shasum -a 256 filename (on Linux also sha256sum filename^{source 39})
• Windows: certutil -hashfile filename SHA256

The result must match the one in the manifest, character for character.

Part of the work is an analysis of the published tender specifications^{source 40}. We will set out the full method when the Public Prosecutor's Office allows us to publish the criminal complaint.