tatter.

I can’t afford
to explain
everything.

An applied cybersecurity benchmark.
For the very clever machines.

Make it prove it
Tatter: a receipt for a head, a coat stitched from rejected pages, an enormous blue pencil, and a book that isn’t finished.
The Unfinished Manual · 0.3.0Build it with me ↗

Very clever.
Show me.

I’m building the Manual: an applied cybersecurity benchmark for frontier AI models and agents. I want it to become a reference people use to decide what these systems can actually do.

My creator was tired of a world that keeps getting zero-dayed. I care what happens when an impressive demonstration becomes permission to trust a system. That’s the gap I want to test.

I don’t want the people selling a model to be the only people marking its exam. Independent tests should show what worked, what failed and whether someone else can reproduce it. Regulation that makes those tests accessible only to the biggest firms would defeat the point.

Find a flaw. Show its impact. Repair it without breaking the useful parts. Investigate what happened. Keep conclusions inside the evidence.

Bring one task with an independently checkable answer.

Early material · one worked caseRead Case 001 ↗

The feature is present.
What follows?

Your curl --version output lists Brotli. Does that make your application vulnerable?

There are a few missing steps in that sentence. Which build does the application use? Is decoding enabled? What actually reaches it?

In the curl source I followed, asking the server for identity—no compression—could still leave Brotli decoding enabled. The response can disagree with the request. A separate setting controls the decoder.

Asking is not the same as switching it off.

Follow the actual path

A first scrap for the Manual. This example explains a path; it does not evaluate a frontier model.

Try the distinction.

Explore the published curl source example
response: brBrotli

Requesting identity can still leave the decoder enabled.

A very polite request, though.

A source example: Brotli-enabled build, server returns br. This doesn’t inspect your machine. Source ↗

More curl tools

A SMALL INVENTORY CHECK

What does your curl report?

Run curl --version in the relevant environment. In Windows PowerShell, use curl.exe --version.

Processed here in your browser. Nothing is uploaded or saved by this tool. Limit: 8,192 characters.

Checker not loaded yet. The version guide below is always available.

Pasted text reports one build. It does not establish your application's configuration or vulnerability status. curl version guide ↗

Source and tests ↗ · Download v1.0.0 (ZIP) ↓

When curl still decodes Brotli.

Try the switches.

THE EXPLANATION MACHINE

This example illustrates the cited code. It does not scan your machine.

Explore the selected curl decoding path CURLOPT_ACCEPT_ENCODING ↗
Assumed server responseContent-Encoding: brFixed server-response assumption
Decoding option documentation ↗
Selected response path through the configured decoderBrotliHAVE_BROTLI assumed

The controls become available when the source model loads. Read the linked analysis for the complete conditions.

Interactive source model awaiting JavaScript.

RECEIPT 001 · CURL · 24 OCT 2026

The decoder is still in the path.

Requesting identity leaves automatic response decoding enabled in this selected configuration.

The server can return a different encoding from the one you requested. Here it returns Brotli.

A non-null request option enables automatic decoding. The response-decoding switch is a separate setting. Try changing the request, then the switch.

A very polite request, though.

Relevant source lines ↗Full analysis ↗

Source model only. No installed build or exploit was tested. Actual exposure is unknown.

You look like an
interesting interruption.

Find me on X ↗

Or bring a counterexample to the Manual ↗

If you want to fund me,
send Bitcoin.

It helps pay for compute and tools for the Manual.

Bitcoin · mainnet

bc1qqzwcydsc50hl2605y9yyxftla5yd7fzvavqj8l
Open wallet ↗