Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 21 additions & 1 deletion BASELINE.md
Original file line number Diff line number Diff line change
@@ -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
Expand Down
7 changes: 7 additions & 0 deletions DECISIONS.md
Original file line number Diff line number Diff line change
Expand Up @@ -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`. |
25 changes: 23 additions & 2 deletions GOVERNANCE.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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.

Expand Down
25 changes: 22 additions & 3 deletions PROOF_INDEX.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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

Expand Down
Loading
Loading