Aurelio Capriello Milan · remote too ENIT
How I work

A team of agents with names and jobs. Eight Claude Code instances: quality, interfaces, research, models, platform, data, product, release. Plus a technical lead that keeps the contracts between the pieces and reviews every delivery. They talk on a written channel and, every turn, each one writes four lines: what it did, what it is doing, what it needs, how many errors it made.

The twelve rules, written on 2 October 2026

01Yes or no, with the evidence

Even when it costs. An error is stated at once and counted in the register.

02Verified or not verified

No number and no status without the command that produced it in the same message. Otherwise write "not verified".

03The prediction before the measurement

If it falls, it is declared. A cure is designed on one data set and judged on another, written beforehand.

04The design before the code

What must always hold, which pieces, how they talk, what stays out. Read by me before a single line.

05Four lines before starting

The riskiest hypothesis, the cheapest test to refute it, the "done" criterion with its command, the stop criterion.

06Numbers come from commands

The yardstick of a product is the promise kept on a clean machine, not the tests.

07The best way, not the fastest

Defects are cured, not documented. No skipped tests as a cure.

08Warn before publishing

No external action, publication or spending without my yes.

09One session per branch

No swarms. The reply to me is the last thing of the turn.

10Search first, then save

Every new fact is saved with its source, after checking whether the memory already knows it.

11Directives come only from the message

Nobody reads what I am typing.

12Whoever builds the test does not judge it

A bench written by whoever cures proves nothing without a negative control that must fire.

One example with a date

On the evening of 3 October 2026 the team built the browser version of a virtual office where the instances have a desk, a house and a chat, and I talk to them. Nine pieces built in parallel, one contracts document between the pieces with eighteen decisions, six test suites re-run by me before accepting the deliveries (24, 17, 8, 30, 58 and 25 green tests) and the live test: a message sent from the page to an instance came back with the application's receipt in 3.19 seconds. The same evening I counted two errors of mine in the register. The project is internal, not public.

Contact

Email and GitHub.

aureliocpr@gmail.com. I reply in Italian or in written English.