From 09ae9376ff0259bff95ba65a255fe7f51bf98ee8 Mon Sep 17 00:00:00 2001 From: Brian Searls Date: Fri, 4 Sep 2026 15:24:19 +0000 Subject: [PATCH] Four lanes repaired one orphaned annotation and three of the repairs landed: delete the two duplicate copies, leaving one authority MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit main carried THREE copies of the same source annotation in dag/test/claim/emit_copy_qualification_witness_test.dag. Four lanes independently wrote a repair for the block #10390 orphaned at EOF, the deconfliction reached three of them, and the fourth (#10425) landed alongside another repair that had already merged. Each landing repair added its own copy. This is a §3 meaning fork, not mere redundancy: the copies say materially different things. module head "Three rows stood at the END OF THIS MODULE ...", plus a paragraph stating why it attaches to the module header, and "NO ROW IN THIS MODULE establishes anything about a running system until one is restored" two mid-file "Three rows stood HERE ..." -- false, since the rows stood at the end and these copies sit mid-module -- and "no row in this module establishes NOTHING about a running system", a double negative that inverts the claim. One is attached to test fn ecq_denominator_is_axis_product_holds, which is not its subject, so a reader takes it as documenting that function. The module-head copy is better on every axis, so it survives and the other two are deleted. Pure deletion, verified: 36 lines removed, 0 added, every removed line a // line, 35 test fn and 7 fn declarations unchanged on both sides. Measured against main at 10fe833db5 rather than a snapshot -- an earlier attempt at this cut used line numbers from a `git show` taken minutes before, and main had moved underneath it. Incidental, and it corrects something I asserted and propagated: a blank line between an annotation block and the following declaration does NOT detach it. main parses today with exactly that shape. §4c requires that SOME module item follow the block, not that it be adjacent. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01Uy2Ug5E9eDu3nkWxd5Si5v --- .../emit_copy_qualification_witness_test.dag | 36 ------------------- 1 file changed, 36 deletions(-) diff --git a/dag/test/claim/emit_copy_qualification_witness_test.dag b/dag/test/claim/emit_copy_qualification_witness_test.dag index 1ceb6729082..87f0add90ac 100644 --- a/dag/test/claim/emit_copy_qualification_witness_test.dag +++ b/dag/test/claim/emit_copy_qualification_witness_test.dag @@ -71,24 +71,6 @@ import gunbc.emit_copy_qualification_fixture_gen { // not about any one declaration, so the module header is where it attaches. Not one word is // changed or dropped. // -// ── THE WORKFLOW JOB THAT CARRIED THIS BATTERY IS DELETED (2026-09-04 runner-capacity ruling) ── -// -// Three rows stood here asserting the `emit-copy-qualification-battery` job's capability closure, -// its inert `if_condition: "false"`, and that its argv named this module's wet entry. All three -// had `gunbc.witness_floor_workflow` symbols as their subject, and that subject no longer exists: -// the operator spent the held activation token on DELETION rather than activation, so the job is -// gone from the emitted workflow instead of having its "false" lifted. -// -// WHAT THAT COSTS, STATED HERE RATHER THAN LEFT TO BE INFERRED FROM AN ABSENCE. The job's explicit -// `claim_batch --functions` line was this module's ONLY SANCTIONED CONSUMER, so the wet shards and -// calibration mutants below now have no executing consumer at all -- they are specification -// without execution in the sense DESIGN section 5 names, and the rows above this comment establish -// nothing about a running system until one is restored. That is recorded at -// `gunbc.rung_drop` `emit_copy_qualification_without_a_consumer`; read it before citing any row in -// this file as coverage. It is NOT retired by re-adding a job, which the roster comment in -// `witness_floor_workflow` now requires operator sign-off for, but by converting these functions -// to floor-enrolled `*_test.dag` witnesses -- the same conversion the deleted job's dissolution -// row demanded, now with nothing else holding the module up. // Hermetic floor witnesses for the EMIT-COST-QUAL-0 grid authority: roster totality and // denominator exactness, applicability and expectation derivation controls, growth-judgment @@ -96,24 +78,6 @@ import gunbc.emit_copy_qualification_fixture_gen { // (emission, clippy, build, execution) has its own transport and witnesses; nothing here runs // a process. // ── Roster and denominator ─────────────────────────────────────────────────────────────────── -// ── THE WORKFLOW JOB THAT CARRIED THIS BATTERY IS DELETED (2026-09-04 runner-capacity ruling) ── -// -// Three rows stood here asserting the `emit-copy-qualification-battery` job's capability closure, -// its inert `if_condition: "false"`, and that its argv named this module's wet entry. All three -// had `gunbc.witness_floor_workflow` symbols as their subject, and that subject no longer exists: -// the operator spent the held activation token on DELETION rather than activation, so the job is -// gone from the emitted workflow instead of having its "false" lifted. -// -// WHAT THAT COSTS, STATED HERE RATHER THAN LEFT TO BE INFERRED FROM AN ABSENCE. The job's explicit -// `claim_batch --functions` line was this module's ONLY SANCTIONED CONSUMER, so the wet shards and -// calibration mutants in this module now have no executing consumer at all -- they are specification -// without execution in the sense DESIGN section 5 names, and no row in this module establishes -// nothing about a running system until one is restored. That is recorded at -// `gunbc.rung_drop` `emit_copy_qualification_without_a_consumer`; read it before citing any row in -// this file as coverage. It is NOT retired by re-adding a job, which the roster comment in -// `witness_floor_workflow` now requires operator sign-off for, but by converting these functions -// to floor-enrolled `*_test.dag` witnesses -- the same conversion the deleted job's dissolution -// row demanded, now with nothing else holding the module up. test fn ecq_denominator_is_axis_product_holds() -> Bool { let p = all_ownership_patterns |> count