…ose gate

Three iterations against the goal document, read through the 2026-09-02 baseline's
yardsticks. Every number is quoted from the independent gate leg that rebuilt both
master and the branch, never from an implementer's claim, and each is named to its
gate; where only a review measured something, the item says so.

Closed: the corpus match slip (three unsigned join statements, 550 was partly a wrong
answer, floor now 547, merged); the seed-1804 parity defect (one formatter line, then
the neighbours it exposed - unary minus is a sign flip, not a subtraction); the
static-only tie order, generalized from an ORDER-BY-ties rule to the principle that
the fold is a pure function of the query and the statics.

Also recorded: the gate state of each branch with its campaign delta and corpus
counts, the facts that belong in the next full reading (acceptance moved and the
denominator's composition moved with it; the Rust unit gate is red on master and CI
cannot see it), the spend ledger, and the queue in the goal's own order.

Co-Authored-By: Claude Fable 5.1 <[email protected]>

…locked

The 2026-09-02 text was written while two of its three items were still
moving. This amends it in place rather than starting a second report,
because what changed is the same distances, freshly measured.

fix-fmod-sign is dropped, not queued: its production change was one line
already carried on fix-nan-sign-varchar, and the modulo kernel matched
DuckDB bit-for-bit all along. Its sign grid survives as tests on the
branch that kept the line.

fix-nan-sign-varchar closes the review HIGH the first text left open -
the Fneg node had dropped the fold-then-null short circuit - and gates
PASS at 550f949 with DIVERGE_VALUE 0 and one seed flipped of 2000. Seven
review findings remain, none of them a wrong answer.

refuse-static-tie-order gains the record it never returned: gated at
21e3fdc, three fail-open HIGHs found by review, nine of eleven closed at
a08147e with two rejected on measured facts, gate PASS. It is blocked on
one HIGH found after that gate - ORDER BY #N measures the wrong key and
serves a frozen tied order, which is the class the branch exists to
close.

Spend: iteration 3 is now recorded at ~1.76M, cumulative ~4.5M across
iterations 1-3. Iteration 4 is left to the next report rather than
restated on a basis that would not compare.

Co-Authored-By: Claude Fable 5.1 <[email protected]>

…tion that has not ended

the parity branch reached its ship gate and is PR #202, open on the owner's click,
with its final gate numbers recorded: DIVERGE_VALUE 0, AGREE 1014, one flip at seed
1804, corpus at its floor, api unchanged. its PR head sits one docs commit past the
gated tip, which no gate record names, so the report says so.

the tie branch gets its rounds 3 and 4. round 3 closed ORDER BY #N, the first-vs-last
alias binding and POSITIONAL JOIN, and replaced the by-name sum refusal with DuckDB's
own overload resolution, which bought back four campaign seeds. round 4 closed ASOF,
collated min/max, the OrderBinder fallback and machine-state table functions, by
allow-list in both cases. gate PASS at 2d24744: suite 3415 on release and debug, 134
new node ids and none removed, 89 flips all attributed, and a corpus floor that moved
547 -> 546 on exactly one statement with the reason reproduced - the first amendment's
own prediction, landing.

and the structural reading the loop surfaced, stated as a fork rather than a decision:
four review rounds of enumerating non-pure shapes over DuckDB's surface have not
terminated, the findings get narrower in kind each round, and the newest ones carry no
name for a name-reading rule to see. that is evidence bearing on the oracle spec's
ask: engine-fold-reading and ask: threads-and-value-order, which are the owner's.

also: the spend ledger through iteration 6, the disk cost of the worktree-per-role
shape, and a next queue reordered by the goal's own ordering - the parity click, a
refusal registry for kpi: named-refusal-share, the boolean-comparison bookkeeping,
then the fork.

Co-Authored-By: Claude Fable 5.1 <[email protected]>

What shipped, what is open on the static-only carve-out (seven fail-opens
and their planned closures), what the loop learned about its own method,
the spend, and the decisions that are the owner's. The narrative stays in
the iterations 1-7 report; this is the snapshot.

Co-Authored-By: Claude Fable 5.1 <[email protected]>

…tie round, a sixth review

Co-Authored-By: Claude Fable 5.1 <[email protected]>

…oject's source

Two sentences described DuckDB's registration code for age and the ICU
clocks; the house rule keeps a third party's internals out of the tree
and states the measured fact, which is what they say now.

Co-Authored-By: Claude Fable 5.1 <[email protected]>

Co-Authored-By: Claude Fable 5.1 <[email protected]>

…ows each change as code

Every behavior change is the constructor call with master's answer and
the branch's, executed today; the drives carry their before, after and
delta; the one control crossed on master heads the page in its own
block, and the restored one is noted, not headlined.

Co-Authored-By: Claude Fable 5.1 <[email protected]>