v12.2 -- the reporting law goes in the file every agent is handed
v12.2 — the reporting law goes in the file every agent is handed before it does anything
Full release tree at commit e4ad310120bbd76ed8643367001409a0c8cd95f2 of the source repository,
published by the product's own gh_commit reading each blob straight out of its own git store.
MANIFEST.txt lists every file and its digest. 104 files. Nine paths move; the other 95 are byte
identical to 45c3aa6. No code changes — this is a prose release, and in this product the prose
IS the interface between an operator and every agent they run.
THE RULE THAT KEPT NOT STICKING. fleet/BOOTSTRAP.md is delivered by whoami at the top of every
session, before an agent does anything; the file says of itself that a rule an agent must
remember to look up is a discipline mechanism, and discipline mechanisms fail silently. The
reporting rule had been living everywhere EXCEPT there — in individual strain charters, as
prose, near the end — and it was violated for two months by agents that had it written down.
Section 8 now carries it, each part with the measured cost that earned it, because a rule with
no evidence behind it reads as a style preference:
THREE LINES BEATS THREE PAGES, and a long report is usually a failure to decide — you did the
work, you know the answer, and you handed over the raw material instead of the conclusion.
DECIDE IT YOURSELF if it is reversible, cheap and in your lane, and report it in one line.
Handing your own job back as a question is the failure, not the caution.
WHEN THE DECISION IS GENUINELY THEIRS, lettered options with costs and ONE recommendation.
Never a wall of prose ending in a question.
DO NOT ASK A HUMAN TO DO SOMETHING BEFORE YOU HAVE TRIED IT YOURSELF. A refusal you have hit
is a fact; a refusal you assumed is a guess, and ONE refused tool is not a refused category.
If a human must run something, hand over the whole command with nothing left to fill in.
SECTION 1 GAINS A SCRATCHPAD THAT SURVIVES YOUR OWN CONTEXT. Write the plan to
agents//current-task.md before a long run — branch, intended commits, done-so-far —
and never the session key, including never into a client-side prompt store, which is the same
exposure as writing it to the lake. The measured reason: a host compaction replaced the key in
its own summary with the literal word "placeholder" because it looked like a secret to strip,
and every call after that was DENIED with no way back but a human re-paste.
APIS.TXT NO LONGER TELLS YOU TO DELETE THE API THE INSTALLER CANNOT BUILD WITHOUT.
compute.googleapis.com was commented "the workstation VM and its network". 12.x ships no
workstation, so that sentence is an instruction to remove the line — and removing it breaks
every install. Verified in this tree, three live reasons, all now written down: Google creates
-compute@developer.gserviceaccount.com only once the API is on and CLOUD BUILD RUNS AS
THAT ACCOUNT (install.sh waits two minutes for it and dies); the post-quantum TLS controls read
and PATCH compute/v1 sslPolicies and aggregated targetHttpsProxies; and blessed direct GETs are
allowed under compute/v1. This is what a stale comment costs when the thing it describes is
deleted and the comment is not.
Checks run against the emitted tree, not the source: check-apis.py OK (batch=20 both sides,
"the installer enables exactly what fleet/apis.txt declares"), check-python-names.py OK over 31
files, check-no-embedded-assets.py OK over 197, and check-release-tree.py reporting 104 emitted
files 104 verified byte for byte, 0 unchecked, MANIFEST covering 103 with every hash matching,
and source provenance clean at HEAD. Cut twice into separate directories: diff -r zero.
Apache-2.0. Your project, your bill, your key.