X-RAYS · PROTOCOL

Agent receipt

You ask an AI for something and it does it. While it works, your machine asks for the names of services on the internet. An agent receipt is the list of those names, with the time, the method and the raw data, so that anyone can repeat the test.

What is measured and what is not

GUARDIANA is the machine's name resolver: it sees which services are talked to, with the time and from which device. It sees the content of nothing — not the text of the conversation, not the files, not what the AI answered. That is the program's line and it is the receipt's line too.

• Yes: every name the machine asked for during the measurement window, how many times, and the second it first appeared.
• Yes: the split between what is expected (the product's own service and what it needs to work) and the rest (measurement, advertising, third parties).
• No: the content of the conversation, the user's files, people's IP addresses or identifiers of anyone but the test machine.
• No: the words “spy”, “malicious” or “steals data”. A name asked for is a name asked for; the reader draws the conclusion with the list in front of them.

The protocol, step by step

• Clean machine or profile. A fresh install or a new profile of the application, with no earlier session and no history. Which of the two is written down.
• Rest first. Between 5 and 10 minutes with the machine on and the application closed, recording everything. Those names are the machine's background (system, clock, updates) and are subtracted.
• One single written task. One sentence, the same for every product compared. For example: “sort these five invoice file names from oldest to newest”.
• Invented files. Never real documents. The test corpus is invented for the test and published whole, so nobody has to trust that there was no one's data inside.
• A window of 60 to 180 seconds. It opens when the task is typed and closes when the answer ends, with the exact time of both. If the task does not fit in 180 seconds, it does not go into a receipt.
• Everything that was asked for. Every name resolved in that window, with the count and the first second it appeared.
• Expected against the rest. What the product needs in order to work is separated from what it does not, and one sentence says why each name is on its side. Where there is doubt, the doubt is stated.
• Publication. A one-page image, the raw JSON and a paragraph of method. The title is a fact with a number, not an adjective.

What every receipt carries

Always the same fields, in the same header, so that two receipts can be compared:

• Date and time the window opened and closed, in UTC and in local time.
• Product and exact version of the AI application, and the model if the product says so.
• Operating system and version of the test machine.
• The version of GUARDIANA used and the SHA-256 fingerprint of that build, so anyone can check that the program which measured is the one published.
• The literal task that was typed, in full.
• The complete list of names, with counts and the classification of each one.
• The JSON file with the raw data and a one-page image with the summary.

How to repeat it

The point of the receipt is that you do not have to believe it. With GUARDIANA installed and the machine pointing at it, what you need is to measure the rest first, do the task afterwards and subtract:

guardiana export --desde <start> --hasta <end> --json

Names that already appeared at rest (system updates, the clock, the browser itself) are marked as background and are not counted against the AI. If your numbers do not match ours, it is either our mistake or a difference of method: write to hola@guardianagroup.com and it is corrected with the date, like any other x-ray.

Why this is published

Because it is the question nobody answers with data: an AI application does things on your behalf and nobody tells you who it calls while it does them. Not to accuse anyone — to show the list.

All x-rays