diff --git a/BASELINE.md b/BASELINE.md index 81c3862b9..914a504fc 100644 --- a/BASELINE.md +++ b/BASELINE.md @@ -1,11 +1,31 @@ # CBZ baseline ledger -**State: Partial Baseline; CBZ-0 is not established.** +**State: active intermediate baseline; CBZ-0 is not established. No terminal Partial Baseline is declared.** This ledger binds the currently observed repository snapshot to the twelve owner criteria and final gate matrix. It records evidence and gaps; it is not a completion certificate. +## Observed integration boundary — 9 November 2026 + +After Main #780 and Workspace #55 landed, the sequentially observed defaults +were Main `b1d36c80403acc96d257b9e71140a6cb83a595af`, Math- +`f532c3e2d91a0c7679a37c733741660917a9b21b`, and Workspace +`8a7aac8626438967830ea5a516a944ce48759018`, whose gitlink pins that Main. +A subsequent Main merge requires another fresh pin comparison. +The source-bound observations, skips, failures and completed post-merge +checks are in [STATUS.md](STATUS.md#observed-integration-boundary--9-november-2026). +A later Main merge requires another guarded Workspace pin refresh. + +All twelve CBZ-0 criteria remain unawarded: complete Git/ref/admin cleanup, +proof dispositions, full Layer A audit, no-skip regression, whole-federation +Lean/kernel/axiom pass, declared mutation threshold, final current pins, +complete self-verified tools, consistent surfaces, STATUS-only cold start and +decisions must be observed together. The known 25 skips, unadopted T10 +proposals and missing final orchestrator remain explicit. This is an active +intermediate ledger, not a terminal Partial or CBZ-0 declaration. Earlier +dated tip descriptions below are historical. + ## Freshness provenance candidate — 9 November 2026 The sequential observed boundary is Main signed merge diff --git a/DECISIONS.md b/DECISIONS.md index bc657fd59..1f23669f3 100644 --- a/DECISIONS.md +++ b/DECISIONS.md @@ -115,3 +115,10 @@ Append-only. Historical source outcomes remain in their original records. | 2026-11-09 18:30 | 2 | B/CI | The post-merge Workspace pins job passed eight network and strict-current pins, four canonical inputs and 187 tests. The post-merge federation workflow failed before any job with GitHub internal-server correlation `63dc5ffa-474e-4405-925b-574e391c43c6`; GitHub refused its failed-job retry with HTTP 403. Preserve both outcomes, do not infer a passing post-merge federation run, and continue other authorized checks. | Yes | Workspace pins run `42674111147`, job `129351557433`; federation run `42674110867`. | | 2026-11-09 17:32 | 2 | B/tooling | Selectively recovered the unchanged tracked-source inventory tool and retained tests from closed-unmerged Main #695, preserving original source authorship instead of creating a new final controller. Missing CLI exit 2 and retained missing-implementation behavioral failure exit 1 were observed first. CPython 3.12.14 then passed 75/75 controls in normal and optimized modes with no top-level skips, errors or failures; each suite exercised nine intended source mutants under the preserved classifier limits. Generate and verify exited 0 over nine explicit local federation checkouts, 27,826 tracked entries and eight gitlinks, with zero classifications. This checks source/state and declared-binding integrity only; recorded clean dirty flags do not award cleanliness, supplied receipt bytes do not authenticate kernel execution, and supplied quarantine strings do not prove isolation or satisfy the complete current governance contract. No historical catalogue, classification or isolation assertion is restored. CBZ flags remain false; no proof, bound, axiom, historical failure, kernel outcome or scientific status changed and no gate or criterion is awarded. Candidate full regression, committed-tree G11 and engineering review remain separate integration checks. | Yes; recoverable ordinary Git addition | Source head `82d9e480a51b946b3e74525ccf32139129d37d28`; recovery parent `5ebe5771d44160f56d4f2fd1e11726858d17dc90`; tool/test blobs `58f5cafbe151f7304ee9ea35b6fc46859d35630f` / `ac8e5edc832ae9ded7ecad134264d3bd1f1871c5`; inventory SHA-256 `c03fcaa8613ff3c853c1cfe0c50f82e05e7a0bb20207a3fe462a722eaab493d3`; normal/optimized focused log SHA-256 `7b3c3f3e6935b83ce071ed425c14bbe65d3d77157b039d3c2253fe0fbf3a3b54` / `35f7e951b52c0bb66bfba579c272c279c654cc506838efa2d365bc34659ebf57`; [recovery scope and commands](docs/cbz/INVENTORY_RECOVERY.md). | | 2026-11-09 17:51 | 2 | B/tooling | Repaired the inventory's real filter-configuration/status race after engineering review demonstrated harmless fixture command execution before a later refusal. A same-size real-Git regression failed against restored source with the executed marker, then passed after status was moved into private fixed detached Git metadata with a bounded regular index copy and explicit common objects. Preflight/postflight refusal remains, but source configuration no longer supplies status filter commands. Added linked-worktree rename/untracked, split-index refusal, ambient/source-info attribute and ignore policy, safe temporary-directory fallback and isolation-bypass mutation controls. The initial parent-directory guard was repaired RED→GREEN with an external `/var/tmp` fallback. CPython 3.12.14/Git 2.52.0 passed 81/81 focused controls per mode with no top-level skips/errors/failures; ten declared mutants were exercised per mode and source digests remained stable. Fresh repaired-tool generate/verify each exited 0 over nine unchanged parent checkouts and 27,826 entries, with zero classifications and false certification flags. Original recovery, reproduced failure, superseded development logs and stopped pre-repair candidate-wide runs remain preserved; no pass credit is assigned to stopped or superseded runs. No proof/catalogue/quarantine, bound, axiom, kernel outcome or scientific status changed; full candidate regression, committed-tree G11 and final federation gates remain separate. | Yes; separate ordinary Git repair from unchanged restoration `1e58f4d9fef8ea9016fc8e46e67a5f7dd33883dd` | Repaired tool/test blobs `2d100b241bc9d8bc6eb5ee6e9b16df229f41c447` / `9eb45d45961169e86c3469ba81f53f5f216bae84`; focused normal/optimized log SHA-256 `81f0dadc2830aa0818724e9c10c5056a2027338fc631fb9a6a045719eda4ffca` / `9058643300f8eb19cd559dfe0418283c7d1a203db6601e36bb781be9bd24eb47`; fresh parent inventory SHA-256 `c03fcaa8613ff3c853c1cfe0c50f82e05e7a0bb20207a3fe462a722eaab493d3`; [repair scope and evidence](docs/cbz/INVENTORY_RECOVERY.md#current-status-filter-isolation-repair--9-november-2026). | +| 2026-11-09 19:00 | 2 | B/integration, status | Record Main #782 and Workspace #54 normal expected-head integration, exact hosted and local execution, 25 preserved Main regression skips, and actual post-merge outcomes. Bound all five canonical surfaces to the sequential pre-documentation observation without claiming final gates; any subsequent Main merge requires another Workspace pin refresh. Historical failed or abandoned workflows, original false kill, proof and scientific boundaries remain unchanged. | Yes | Main `f1ef3a2babecca0f0d4eb35b018dc81d30e9d62c`, tree `5b771047cb384a9bb167ed2df505489cee1cbf7d`; Workspace `1c552538e6a8952548e2bd5297a0031dda1f94e7`, tree `e069b39ba25ffc2e3c6e2838a9b53c1e4e8484a6`; checkpoint v152 SHA-256 `0158242067489b021eb889714684e4cbb6f8334871aeb10b0332b52bc0ffd839`; board #738 comment 6748667855. | +| 2026-11-09 19:00 | 2 | B/accounting | Independently reproduced the T10 normalization and proposal records byte for byte; independently checked 46 quotations across five selected records, and restored all 1,872 bound source blobs through a selective native-object pack without network. The pack is not a full ref/history backup; no branch deletion, adoption, logical isolation or scientific review is implied. Preserve the initial ad hoc pack-script SyntaxError and its corrected result. | Yes; retained source and selective pack | Source Main `fd77339a5e4f6f27704f69b3082e31da90fb1dcd`; records SHA-256 `2ee2f0e5d9784cfee824450efb7f8c35f9f89f2dc1199451b913122613b28722`; read-back supplement SHA-256 `2bebe703fba2b7538e127182fb91dbd4c32d2a53ecf0d768982cb94c62a0a10a`; [readback](https://github.com/d6g8k5htny-coder/main/issues/684#issuecomment-6748666194). | +| 2026-11-09 19:01 | 2 | B/publication | The ordinary Main #782 workflow deployed the qualified site artifact and observed the public publication receipt for 32 snapshots. The separately retained rendered Chromium report recorded 39/39 cases and zero page errors, within its physical-device and screen-reader limits. This publication does not establish scientific acceptance, proof closure or the STATUS-only cold start. A first receipt-bundle restore attempt failed because the prerequisite was not connected to a ref; after connecting the exact prerequisite, a fresh unbundle retained the two receipt commits and blobs even with alternates removed. Preserve both outcomes. | Published; receipt history retained | Run `42677287313`, deploy job `129367351564`; source `f1ef3a2babecca0f0d4eb35b018dc81d30e9d62c`; prepared receipt `29a8b2be282ebfe02c2bc71743ac477a63f74842`, observed receipt `4a92fb8a90fa2f0a54ffdd1b009e0771201c0fe9`; metadata artifact SHA-256 `5088130f7dd1d6b0c716651905b09bfa7bd73628e6d46a0a010381c978be9fb4`; state artifact SHA-256 `7ef72f47e85b03ba10f807b307bfad0e7a33ca059d762706e4d6df89e9c18a98`. | +| 2026-11-09 19:08 | 2 | B/conflict, accounting | A non-admitted T10 structural probe found all eleven named fields nonempty and refused 26 adverse malformed-input controls in each mode. It did not verify semantic accuracy, mathematical blocking reasons, logical isolation or adoption. Proposals 019, 020 and 049 mention absent or unresolved review/novelty alongside source or proof limitations; preserve that history while treating missing procedural review alone as no mathematical blocker under the owner directive. No record was modified or promoted. | Yes; evidence-only probe | Input SHA-256 `2ee2f0e5d9784cfee824450efb7f8c35f9f89f2dc1199451b913122613b28722`; probe supplement SHA-256 `fb4d20e9a6e653e589e3e93cf053026ba73aa290367aba9309cecb5958ed6bcb`; main#684 comment 6748878712. | +| 2026-11-09 19:16 | 2 | B/tooling, conflict | Preserve an independent adverse assertion-origin finding on unmerged Main #780. At its exact observed head, 20 selected original-source baselines passed; 16 combined nominal-mutation and subject-assertion selected children satisfied RF312/replay/status classifier conditions in both modes. Two inventory mutations on their actual full-suite path also yielded four accepted adverse children, each reporting 81 tests, 95 failures and four controller skips. The historical mutant runs are not reclassified. The candidate remains unadmitted; future classifier evidence requires actual pre-cleanup selected-test/oracle code provenance and fresh adverse qualification. No peer source or mathematical disposition changed. | Yes; source and failure logs retained | Head `24ad8a143862fb9255fc6e2e7bf08c12f989f71d`; selected evidence SHA-256 `b66a035e7ffa6fb59aef3ea2b0af98bc35b1d6fede527b581a1d00b53df00a0f`; full-suite evidence SHA-256 `29c6295898ab74f1a3e657a60cbc38297bd9411e65e0df07713dd1539fbc2733`; [peer report](https://github.com/d6g8k5htny-coder/main/pull/780#issuecomment-6749064045). | +| 2026-11-09 19:30 | 2 | B/integration, conflict | Main #780 landed as an ordinary merge after the assertion-origin adverse finding; the recovered inventory source and its documented bounded source/state use are retained. Its mutation classifiers are not admitted as sound by that merge or by historical counts. Preserve both branches' appended decision records, the false-kill evidence, the separately reported Node regression and all prior outcomes. Workspace still pins the earlier Main and requires a guarded refresh. Subsequent integration requires fresh source and checks. | Yes; normal Git composition | Main `b1d36c80403acc96d257b9e71140a6cb83a595af`, tree `10bc30f82661ebdd763384496afffbe7f575459a`, parents `f1ef3a2babecca0f0d4eb35b018dc81d30e9d62c` and `24ad8a143862fb9255fc6e2e7bf08c12f989f71d`; [Main #780](https://github.com/d6g8k5htny-coder/main/pull/780); Workspace `1c552538e6a8952548e2bd5297a0031dda1f94e7`. | +| 2026-11-09 19:44 | 2 | B/integration, pins | Workspace #55 integrated through hosted required checks and a fresh expected-head merge, updating only the Main gitlink, pin, README and appended decision. The tested merge tree equals the published tree; prior source and seven other pins remain. Both hosted modes ran 187 tests without skips; strict-current pins and canonical inputs passed at the observed pre-merge interval. This does not establish final G7 or a full federation matrix. A later Main merge requires a fresh pin comparison. | Yes; ordinary Git history | Workspace `8a7aac8626438967830ea5a516a944ce48759018`, tree `d8db9ab8dd764d6f564b1d46fee03990be7b770a`, tested merge `238b379f671b0d0f0d4c471befdfa7dc1ebf4c35`; Main `b1d36c80403acc96d257b9e71140a6cb83a595af`; premerge evidence SHA-256 `4d2b668a2e62a8ea1beeb627e89229cd512b7a4fe79fdd937257d84cb12659fc`. | diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 0393c631d..8b4b0478f 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -18,6 +18,27 @@ Its team-model sections 1.5, 7.4 and 8 supersede older exclusive-owner and monitor-specific integration restrictions. Historical decisions retain their original timestamps and outcomes; the latest directive controls future action. +## Observed freshness integration — 9 November 2026 + +Main #782 and Workspace #54 integrated through normal expected-head checks. +Workspace #55 subsequently refreshed the Main pin through the same guarded +process; the sequential observation and limits are in STATUS. +Main #780 later landed its bounded source inventory; its mutation classifiers +remain unqualified under the adverse assertion-origin evidence. The inventory +purpose, exact commands, verification and limits are registered in +[TOOLING.md](TOOLING.md#recovered-tracked-source-inventory--9-november-2026). +The sequential source boundary, executed checks, retained failures and +post-merge limits are in [STATUS.md](STATUS.md#observed-integration-boundary--9-november-2026). +The selected-body provenance rule below is now used by the landed freshness +mutation component; its old false kill stays historical. No scientific review, +whole Layer A clearance or final G0–G11 pass is implied. A subsequent Main +merge requires a guarded Workspace pin refresh, and actual platform +protections remain binding. The retained T10 field-shape probe is evidence +only: nonempty fields cannot establish a mathematical obstruction or logical +isolation, and missing procedural review alone is not a mathematical blocker. +Its exact commands and limits are in [TOOLING.md](TOOLING.md#t10-structural-readback-probe--9-november-2026). +This section supersedes older dated statements about current tips below. + ## Freshness mutation provenance candidate — 9 November 2026 An assertion is an admissible kill for the node-status freshness mutation @@ -30,8 +51,8 @@ historical results are not rebound. The new bounded control's purpose, commands, verification and limits are registered in [TOOLING.md](TOOLING.md) and its current observation in [STATUS.md](STATUS.md). These controls are not an adversarial process sandbox or mathematical/scientific review. -Workspace #53's guarded merge pins the then-current Main `6ab126be…`; -the newer Main freshness repair remains a draft. Later integration must use +Workspace #53's guarded merge pinned then-current Main `6ab126be…`; +the freshness repair was a draft at that earlier observation. Later integration must use fresh heads and normal required checks, preserving the recorded platform failures. Older dated descriptions of current tips below are historical. diff --git a/PROOF_INDEX.md b/PROOF_INDEX.md index 8c5538918..418b91862 100644 --- a/PROOF_INDEX.md +++ b/PROOF_INDEX.md @@ -8,6 +8,25 @@ into a kernel proof. A theorem is CLOSED only for the literal statement and allowed-axiom boundary actually checked. Anything else must remain OPEN or be placed in a complete dormant quarantine. +## Observed integration proof boundary — 9 November 2026 + +The landed Main #782 freshness repair, Main #780 source inventory and +Workspace #54 and #55 pin updates are engineering and custody changes. They do not change, close, refute or rebind +any mathematical statement, bound, axiom, hypothesis, proof, quarantine, +kernel result or scientific disposition. The current observed source boundary +is described in [STATUS.md](STATUS.md#observed-integration-boundary--9-november-2026). + +The independent T10 readback checked byte reproduction and selected source +quotations for 65 proposed records; it did not prove the proposals complete, +logically isolated or scientifically accepted, and did not adopt them. A +separate structural-only check found all eleven fields present; it did not +validate their mathematical meaning. Proposals 019, 020 and 049 mention +review or novelty in blocking-reason text alongside source/proof limits; +missing procedural review itself is not a mathematical blocker. The +selective source-object pack is not a full history backup. Whole-federation +proof inventory and final kernel/axiom checks remain unawarded. This section +supersedes older dated descriptions of current tips below. + ## Freshness repair proof boundary — 9 November 2026 The candidate described in @@ -18,9 +37,9 @@ quarantine, kernel result, historical mathematical statement or scientific disposition. The retained original false kill concerns mutation evidence, not the mathematical statements. -The current sequential Workspace merge `2441baf0…` pins Main `6ab126be…`; -the freshness repair remains a separate Main draft. This observation -supersedes older dated descriptions of current tips below. +At that earlier observation, Workspace `2441baf0…` pinned Main `6ab126be…`, +and the freshness repair was a separate Main draft. The later integration is +recorded above. ## Navigation history candidate boundary — 9 November 2026 diff --git a/STATUS.md b/STATUS.md index b218341e4..0cf8c2bbf 100644 --- a/STATUS.md +++ b/STATUS.md @@ -1,6 +1,6 @@ # CBZ-0 execution status -**State: Partial Baseline; CBZ-0 is not established.** +**State: active intermediate baseline; CBZ-0 is not established. No terminal Partial Baseline is declared.** This entry adopts the owner's expanded [Master Directive](governance/MASTER_DIRECTIVE_20261029_SWARM.txt) and [team protocol](GOVERNANCE.md#team-structure-and-coordination). @@ -8,6 +8,170 @@ The inherited scientific material below is explicitly the 29 September snapshot, not a fresh CLOSED decision or an empirical-validation receipt. Its mathematical statements, source cuts and review limits are preserved. +## Latest observed inventory integration — 9 November 2026 + +Main #780 merged at 19:26 UTC as `b1d36c80403acc96d257b9e71140a6cb83a595af`, +tree `10bc30f82661ebdd763384496afffbe7f575459a`, with parents `f1ef3a2b…` +and `24ad8a143862fb9255fc6e2e7bf08c12f989f71d`. Workspace #55 subsequently merged at 19:43 UTC as +`8a7aac8626438967830ea5a516a944ce48759018`, tree +`d8db9ab8dd764d6f564b1d46fee03990be7b770a`, with parents `1c552538…` and +`9f0fbbbb615c7d39207f7bfaef3fd53a7e561fc3`; its Main gitlink now pins +`b1d36c80403acc96d257b9e71140a6cb83a595af`. The tested merge +`238b379f671b0d0f0d4c471befdfa7dc1ebf4c35` had that exact tree. Hosted +job `129389209449` passed eight strict-current pins, four canonical inputs +and 187 tests; job `129389215646` ran 187 tests in each Python mode without +skips. Local strict pins and canonical inputs also passed; local normal +regression ran 187 tests without skips, while its optimized run was still in +progress at this observation. These are sequential observations, not final +G7. Post-merge jobs require their own observed outcomes. A later Main merge, +including this documentation change, requires another guarded pin comparison. + +The recovered inventory CLI is present in the merged source, with commands and +scope in [TOOLING.md](TOOLING.md#recovered-tracked-source-inventory--9-november-2026). +Its ten historical designated mutation counts remain subject to the adverse +assertion-origin findings described below. The merge does not qualify those +classifiers as sound. No historical test or mutant outcome is reclassified. +The #780 author separately reported a Node run with 766 passes and one failure +among 767 cases; this report is not a passing full regression and must be +preserved and independently resolved or isolated. See [Main #780](https://github.com/d6g8k5htny-coder/main/pull/780). + +The 41 T10 branch histories have since been retained in a self-contained Git +bundle with 17,990 reachable Git objects, restored without network or +alternates and checked with `git fsck`; this does not adopt any proposal, +include external LFS payloads or separate submodule repositories, or authorize +remote branch removal. Bundle SHA-256 +`d44d3d2d81be98ca27fbc2636a3a34d8d486ce1e64a8a12830a214880c6ae284`, +Library ID `libfile_fde3_f-19a1ea0bf3ec81918654bfd1baefd2e4_59a0f9f234e48191bc19fddcc0f80648`; +restore evidence SHA-256 `1ffc5edf89390caa6e65d587bddcf3d16dfc61247013dc55880e25503b42e7a6`. +A later nine-repository public ref snapshot found 2,067 heads and 39 tags in +separate observation intervals; all 41 recorded Math heads matched and eight +Workspace pins matched the then-observed defaults. It does not establish +current pins after #780, clean Git, full PR/admin inventory, safe deletions, +proof truth or final G7/G10. The raw snapshot and independent parse readback +are `libfile_fde3_f-38ba247049888191b936dde2c664f54a_59a0f9f234e48191bc19fddcc0f80648`, +SHA-256 `8c7b6fc75f1a4b9218361adb44895166ec6b6dfc3b5e61893367b730e50e5efd`. + +## Observed integration boundary — 9 November 2026 + +This section records sequential observations through 19:02 UTC, before this +documentation change. Main #782 merged as +`f1ef3a2babecca0f0d4eb35b018dc81d30e9d62c`, tree +`5b771047cb384a9bb167ed2df505489cee1cbf7d`, with parents `6ab126be…` and +`9bf048e9aeee3b846da92fba6e4d0708dee310e7`. Workspace #54 merged as +`1c552538e6a8952548e2bd5297a0031dda1f94e7`, tree +`e069b39ba25ffc2e3c6e2838a9b53c1e4e8484a6`, pinning that Main commit. +Math- was `f532c3e2d91a0c7679a37c733741660917a9b21b`. These observations +were not simultaneous. A later Main merge, including this documentation +change, requires another guarded Workspace pin refresh before current-tip +agreement may be claimed. The older dated sections below remain historical. + +The repaired freshness mutation grader rejects the real subject-origin false +kill; the original failure and all eleven original mutations remain. Current +Main #782 hosted controls job `129353108258` passed 20 focused controls, +eight designated guard detections and 22/22 authorized original-mutation +kills in each parent mode, with real subject-origin refusal in both child +modes. This is selected synchronous unittest and named-pattern evidence, not +a hostile-child sandbox, full Layer A audit or final G0/G6. Its bounded +commands and limits are in [TOOLING.md](TOOLING.md). The old false-kill +result is not retroactively rebound. The `eng.hard-gate` engineering record +remains explicitly stale under the cited-content check; its historical source +pin is preserved. A strict freshness check is expected to return nonzero +while that observed drift remains. + +At earlier native tree `1c765f1aae84cd91c2d26706b967690b73823e2c`, full +local discovery completed 2,489 tests in each Python mode with 25 explicit +skips each. At the current tested Main #782 merge, hosted navigation ran +2,489 tests with 25 skips and a separate 20 history tests without skips. The +25 local skips comprised five restricted-container checks, two browser +checks, two Lean-dependent checks, one historical composition check, four +real-record checks with no applicable fields, one real-record live-source +comparison not performed, and ten pytest-dependent checks. Other separately executed controls do not turn these into one +no-skip run. Criterion 5 remains unawarded. Exact logs and limits are in +checkpoint v152 and the independently read-back supplement +`libfile_fde3_f-9cfc31236cd88191b63533d7eb3b0729_59a0f9f234e48191bc19fddcc0f80648`. + +Workspace #54's exact-head hosted federation job ran 187 tests in both modes +without skips; its pins job passed eight network and strict-current pins, +four canonical inputs and 187 tests. Local exact-tree tests also ran 187 per +mode without skips. Its post-merge pins job `129366156775` passed the same +eight current pins, four canonical inputs and 187 tests; the separate +post-merge federation job `129366157128` subsequently ran 187 tests in +each mode without skips. Main's post-merge required aggregate job +`129366584981` reported success at `f1ef3a2b…`. Its current-site deployment +job `129367351564` completed: the published-source receipt was prepared at +`29a8b2be282ebfe02c2bc71743ac477a63f74842` and observed at +`4a92fb8a90fa2f0a54ffdd1b009e0771201c0fe9` for 32 snapshots. The hosted +rendered Chromium report recorded 39/39 passing cases and no page errors; +this is bounded emulation, not physical-device, complete screen-reader or +scientific certification, nor the STATUS-only cold-start test. Previously +failed GitHub startup, abandoned-job and retry outcomes remain recorded +below and are not replaced by later successes. + +Independent mechanical T10 readback reproduced 65 **proposed** obligation +records and 559 other items byte for byte from retained source. It matched +all 46 source statements in five selected records. A restored selective +Git-object pack resolved all 1,872 recorded source bindings; it is not full +ref/history retention and authorizes no branch deletion. Those proposals +have not thereby been adopted or shown mathematically isolated, closed or +scientifically accepted. The exact source, logs and selective pack were +independently read back from +`libfile_fde3_f-5a2970c2901881918ed36aad44f1610a_59a0f9f234e48191bc19fddcc0f80648`, +SHA-256 `2bebe703fba2b7538e127182fb91dbd4c32d2a53ecf0d768982cb94c62a0a10a`. +A later structural-only readback found nonempty, basic-type values for all +eleven required fields in the 65 proposals, with 26 adverse malformed-input +controls refused in each mode. This does not establish the truth of any +field, an exact mathematical boundary, a blocking reason or isolation. +Proposals 019, 020 and 049 mention absent or unresolved review/novelty in +their blocking-reason text alongside source or proof limits. Those historical +notes remain, but missing procedural review alone is not a mathematical +blocker. The scope, commands and retained probe are in +[TOOLING.md](TOOLING.md#t10-structural-readback-probe--9-november-2026). + +At the earlier read-only #780 A8 probe, the then-unmerged inventory candidate at +head `24ad8a143862fb9255fc6e2e7bf08c12f989f71d` accepted subject-origin +`AssertionError` failures under its mutation classifiers. Twenty selected +original-source baselines passed; sixteen combined nominal-mutation and +subject-assertion selected children met the RF312/replay/status classifier +conditions in both modes. The two older inventory conditions also accepted +all four full-suite adverse children, each reporting 81 tests, 95 failures and +four controller skips. These are adverse probes, not the historical mutant +results; those outcomes remain unchanged. The test-name and message checks do +not establish selected-oracle origin. The landed inventory classifier must +qualify any later provenance repair and its own tests before future mutation +counts are treated as sound. Source, baselines and raw adverse logs are +retained in separately read-back evidence files identified in DECISIONS. +No peer branch or mathematical disposition was changed by the probe. + +For available bounded checks, from a Main checkout run: + +```sh +python3 -B -S -m unittest tests.test_node_status_mutation_grader -v +python3 -B -O -S -m unittest tests.test_node_status_mutation_grader -v +python3 -B -S cbz/evidence/node-status-freshness/run_mutations.py +python3 -B -O -S cbz/evidence/node-status-freshness/run_mutations.py +python3 -B -S tools/cbz/g11_census.py --rev HEAD --json /tmp/cbz-g11.json +python3 -B -O -S tools/cbz/g11_census.py --rev HEAD --json /tmp/cbz-g11-opt.json +python3 -B -S tools/node_status_refresh.py records/node_status --check +python3 -B -S -m unittest discover -s tests -p 'test_*.py' -v +``` + +From the Workspace checkout, run `python3 tools/verify_pins.py +--require-current` and `python3 tools/verify_canonical_inputs.py`. These +commands need the documented dependencies and network where applicable. +They do not implement the complete G0–G11 matrix; no single documented +command currently runs that final pass. Retain actual skips, errors, sources +and exits. The proof index, quarantine inventory, whole Layer A audit, +full regression, final kernel/axiom pass, mutation threshold, final pin and +Git/admin inventory, tooling admission, consistent surfaces and STATUS-only +cold start have not been observed together. No CBZ-0 or terminal Partial is +claimed. + +At 19:06 UTC the independently read-back contribution checkpoint was version +153, SHA-256 `ed780a4dd034b648f96d8e959587ef17f0270d5a85e65b52fdbfb82f1df5c7e4`; +later versions may exist. +The original large evidence ZIP remains at its v139 identity and SHA; newer +supplements are separate, not a matched replacement. + ## Freshness provenance repair candidate — 9 November 2026 Main #779 merged as signed `6ab126beda65e19865b8468b52f8757ac2324e1f`, @@ -17,7 +181,7 @@ native source commit `9486c850d0c22fd1438e18fb392dbe02d7bd214f` has tree `d9a794488b34168cad49580a40460b44a5b33dfd`. Draft Main #782 hosted head `c65dc2d3ee52038a0804f6c7455ff8b5844d17ab` tested synthetic merge `0f76c40fac38af52aed6b32693bb3e1c6ea902d3`, tree -`cfc7bca8d65eec3592e22be0530ddbdcc406f134`; it is not yet integrated. +`cfc7bca8d65eec3592e22be0530ddbdcc406f134`; at that earlier observation it was not yet integrated. The later integration is recorded above. Workspace #53 merged as signed `2441baf051312878ca28e462d455cfbcd8e91b20`, tree `13dd6b73201627177c568cb4233a33fb60acbbab`, pinning Main `6ab126be…`. @@ -61,8 +225,7 @@ contains the eight expected files: 20 controls, eight guard detections and refusals in both child modes. This observed component is not final G0 or G6. The exact native composed-tree G11 censuses passed in both modes with 69 tools, zero failing tools and zero skips; that is not the final federation G11 gate. -The full local regressions were still running. Inspect all checks at any later -candidate head. +At that earlier observation the full local regressions were still running. Their later outcomes are recorded above. The hosted navigation workflow `42673203393` failed before jobs with a GitHub internal-server annotation; its failed-job retry was refused with diff --git a/TOOLING.md b/TOOLING.md index 4365fabf0..484dda5d6 100644 --- a/TOOLING.md +++ b/TOOLING.md @@ -2,13 +2,69 @@ **State: component registry; the final federation toolchain is incomplete.** -This file lists runnable mission-relevant tools present in Main. The current -documentation candidate is based on signed Main -`6ab126beda65e19865b8468b52f8757ac2324e1f`; older source-parent bindings are -preserved in their dated sections as history. Each entry states purpose, +This file lists runnable mission-relevant tools present in Main. The latest +observed integration boundary is recorded below; older source-parent bindings +are preserved in their dated sections as history. Each entry states purpose, command, verification and scope. A component passing in isolation does not complete a CBZ gate or the final G0–G11 matrix. +## Observed freshness tool integration — 9 November 2026 + +The node-status provenance guard below landed through Main #782. Workspace +#55 later refreshed the Main pin; its sequential observation is in STATUS. +Current-head +hosted controls job `129353108258` exercised 20 focused controls, eight +designated guard detections and 22/22 authorized original-mutation kills per +parent mode, including real subject-origin refusals in both child modes. Its +commands, original false kill and bounded synchronous-unittest scope remain +documented below; historical outcomes are not rebound. See +[STATUS.md](STATUS.md#observed-integration-boundary--9-november-2026) for +the source boundary, current stale record, retained failures and final-gate +limits. This section supersedes earlier dated current-tip descriptions. + +## T10 structural readback probe — 9 November 2026 + +**Purpose and scope:** a one-off, non-admitted evidence probe checks that +the eleven named fields exist with basic nonempty types in the retained T10 +proposals, that owner is `none`, maintenance is `zero`, and ids are unique. +It does not evaluate truth, mathematical blocking reasons, exact boundaries, +logical isolation, scientific review or adoption. The source and reports are +in separately read-back Library file +`libfile_fde3_f-765237bb3abc8191a41b33747a6fc852_59a0f9f234e48191bc19fddcc0f80648`, +SHA-256 `fb4d20e9a6e653e589e3e93cf053026ba73aa290367aba9309cecb5958ed6bcb`. +Its input `records_verified_t10.json`, SHA-256 +`2ee2f0e5d9784cfee824450efb7f8c35f9f89f2dc1199451b913122613b28722`, is in +the retained T10 readback supplement named in STATUS. + +**Commands:** after extracting those two retained artifacts into the same +working directory and supplying a new output path: + +```sh +python3 -I -B check_fields.py records_verified_t10.json t10-fields-normal.json +python3 -I -B -O check_fields.py records_verified_t10.json t10-fields-optimized.json +cmp t10-fields-normal.json t10-fields-optimized.json +``` + +**Observed verification:** 65 records had no structural errors; the probe +refused 26 missing, null, invalid-value or duplicate-id controls in each mode, +and both reports were byte-identical. Its literal review-word matches are +flags for interpretation, not semantic judgments. This is not a federation +auditor, a source-mutation qualification or a final gate. + +## Landed inventory classifier boundary — 9 November 2026 + +Main #780 landed as `b1d36c80403acc96d257b9e71140a6cb83a595af` with its +tracked-source inventory CLI and its documented bounded scope. At its observed +head `24ad8a143862fb9255fc6e2e7bf08c12f989f71d`, an isolated A8 probe +showed that subject-origin assertions could satisfy its mutation-result +conditions, including the full-suite inventory conditions. This does not +change or refute the earlier historical mutant runs. Future mutation counts +need actual pre-cleanup traceback/code provenance and explicitly authorized +test or oracle origins, plus fresh adverse checks. Exact observations and +source-bound evidence are in [STATUS.md](STATUS.md#observed-integration-boundary--9-november-2026) +and DECISIONS. The inventory source is present; its mutation classifiers are +not admitted as sound and provide no final G0 or G6 qualification. + ## Node-status freshness origin guard candidate — 9 November 2026 **Purpose:** reject false mutation kills caused by failures in the subject,