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
23 changes: 23 additions & 0 deletions BASELINE.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,29 @@ Neither a successful recovery nor a successful new publication is inferred.
The source-bound local tests and mutation campaign are scoped in TOOLING;
no proof, scientific or final baseline status changes.

## Selected historical text custody candidate — 10 November 2026

This candidate preserves exact Git head/tree objects and selected changed
head-side text blobs from 430 historical public Main and Math refs: 588 Main
`.lean` blobs and 608 Math `.lean`/`.md` blobs, with 6,867 head/path bindings.
The case-sensitive suffix selection, separately observed defaults, exact
identities and exclusions are in the [custody record](cbz/evidence/public-selected-text-custody-20261110/README.md). It does not
preserve deleted default-side blobs, unchanged files, other suffixes, Gitlink
contents or private refs. Ref currency, semantic uniqueness, proof status,
logical isolation and scientific acceptance are not inferred. No ref is
removed.

A fresh copy of the packaged record checked all 24 checksums, completed four
Main/Math cold readbacks in normal and optimized Python modes, and ran the
specified adverse driver: two clean passes, 30 altered-selection or source
record rejections, four detected verifier-mutant executions and two damaged-pack
rejections. These are bounded source-custody controls, not a complete Layer A
auditor, proof inventory or final G0/G10 gate.

Exact commands and observations are in [STATUS](STATUS.md#selected-historical-text-custody-candidate--observed-10-november-2026)
and [TOOLING](TOOLING.md#selected-historical-text-custody-readback--10-november-2026).
No proof, quarantine, scientific acceptance or final gate is awarded.

## Public branch custody candidate — 10 November 2026

This candidate preserves selected public Git objects from 58 captured refs in
Expand Down
61 changes: 61 additions & 0 deletions DECISIONS.md
Original file line number Diff line number Diff line change
Expand Up @@ -799,3 +799,64 @@ Author-family correction1 moves only the two runner.temp bindings into prepare-s
`129618510111`, `129618705245` and `129618849837` remain preserved
on the selected-text custody candidate. These observations do not perform
an authenticated receipt write or establish a final gate.

[2026-11-10] [Phase 2] [Layer B / source custody] Preserve the separately
observed 430 public Main and Math historical refs, their exact head/tree
objects and the selected changed head-side `.lean` and `.md` blob packs under
`cbz/evidence/public-selected-text-custody-20261110/`. Verify the stated
selection and each preserved object in both Python modes; retain the specified
adverse executions and their original results. Scope excludes deleted
default-side data, unchanged content, Gitlink targets, other suffixes and
private refs. Source identity is not a proof, quarantine, semantic uniqueness,
scientific review or permission to remove a ref. Reversible: additive isolated
candidate; prior source and historical outcomes remain. Evidence: package
README, SHA256SUMS and retained verification history.

## 2026-11-10 — Compose selected text custody after publication candidates

- Preserve the complete publisher/recovery and Main #799 decisions prefix,
followed by the exact prior selected-text custody decision. The source packs,
selected records and their historical readbacks remain unchanged.
- This is a staged composition on the publication candidates, not an
integration or a new proof, quarantine, scientific or final-gate claim.
Recheck the actual base, exact tested tree and required checks before merge.

## 2026-11-10 — Preserve failed architecture preparation observation

- [Layer B / adverse evidence] Preserve Main #800's actual architecture and
intake failures plus the bounded read-only diagnostic source and decoded
job logs under `cbz/evidence/architecture-artifact-observation-20261110/`.
The diagnostic checked one retained ZIP digest, native run/commit identity
and one result member; it did not qualify architecture or any final gate.
- The artifact reported unsafe/private daemon configuration, no completed
daemon mutation, and no recovery error. Retain the failure and its limits;
do not disclose the daemon configuration or disable the affected checks.
- Preserve the diagnostic commit as an additional candidate parent and retain
its workflow as evidence rather than enabling it on the candidate. This is
reversible and does not alter any default ref or scientific claim.

## 2026-11-10 — Preserve publication artifact readback and inspection failures

- [Layer B / tool evidence] Retain the two recomposed publication/recovery
component logs, the bounded archive-readback source and all four actual
readback attempts under
`cbz/evidence/publication-artifact-observation-20261110/`. The successful
readback checked exact artifact digests, CRCs, tested-source hashes, unit
outcomes and selected mutation-origin records; it is scoped component
evidence, not a deployment or final G0--G11 pass.
- Keep the earlier readback failures: one selected test emitted two authorized
events and the initial reader assumed one; a later reader inferred a mutant
file extension from its label. The corrected reader checks every selected
event and requires one recorded mutant source. Original component outcomes
are unchanged. Preserve the diagnostic ancestry and its source as evidence,
not an active workflow or a new general-purpose certifier.

## 2026-11-10 — Compose selected custody after Main #803

- Preserve the entire latest publisher/recovery/#803 decisions prefix,
followed by the exact selected-text and diagnostic evidence suffix. Keep
selected source package tree `60eb8f16164f11aee59fcd38bcf7e777b8cea2ce`
and all historical failure and readback records. No source ref is removed.
- Recheck the current base, exact tested tree, required checks and live
federation pins before integration. These custody and diagnostic records
do not establish mathematical, scientific or final-gate status.
23 changes: 23 additions & 0 deletions GOVERNANCE.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,29 @@ and [tool registry](TOOLING.md#guarded-pages-receipt-recovery--10-november-2026)
give exact commands, observations and limits. This is neither mathematical nor
scientific acceptance and does not establish the final gates.

## Selected historical text verifier boundary — 10 November 2026

This candidate preserves exact Git head/tree objects and selected changed
head-side text blobs from 430 historical public Main and Math refs: 588 Main
`.lean` blobs and 608 Math `.lean`/`.md` blobs, with 6,867 head/path bindings.
The case-sensitive suffix selection, separately observed defaults, exact
identities and exclusions are in the [custody record](cbz/evidence/public-selected-text-custody-20261110/README.md). It does not
preserve deleted default-side blobs, unchanged files, other suffixes, Gitlink
contents or private refs. Ref currency, semantic uniqueness, proof status,
logical isolation and scientific acceptance are not inferred. No ref is
removed.

A fresh copy of the packaged record checked all 24 checksums, completed four
Main/Math cold readbacks in normal and optimized Python modes, and ran the
specified adverse driver: two clean passes, 30 altered-selection or source
record rejections, four detected verifier-mutant executions and two damaged-pack
rejections. These are bounded source-custody controls, not a complete Layer A
auditor, proof inventory or final G0/G10 gate.

The exact command and tool scope are registered in
[TOOLING](TOOLING.md#selected-historical-text-custody-readback--10-november-2026)
and [STATUS](STATUS.md#selected-historical-text-custody-candidate--observed-10-november-2026).

## Public branch custody verifier boundary — 10 November 2026

This candidate preserves selected public Git objects from 58 captured refs in
Expand Down
16 changes: 16 additions & 0 deletions PROOF_INDEX.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,22 @@ prepared candidate is retained in receipt ancestry, and no successful recovery
or publication is inferred. See the dated STATUS entry for actual observations
and TOOLING for commands and verification limits. This entry closes no proof.

## Selected historical text custody boundary — 10 November 2026

This candidate preserves exact Git head/tree objects and selected changed
head-side text blobs from 430 historical public Main and Math refs: 588 Main
`.lean` blobs and 608 Math `.lean`/`.md` blobs, with 6,867 head/path bindings.
The case-sensitive suffix selection, separately observed defaults, exact
identities and exclusions are in the [custody record](cbz/evidence/public-selected-text-custody-20261110/README.md). It does not
preserve deleted default-side blobs, unchanged files, other suffixes, Gitlink
contents or private refs. Ref currency, semantic uniqueness, proof status,
logical isolation and scientific acceptance are not inferred. No ref is
removed.

The preserved bytes are source custody only. No new CLOSED claim or dormant
quarantine is admitted, and historical mathematical statements, authorship,
outcomes and failures remain as originally recorded.

## Public branch custody boundary — 10 November 2026

This candidate preserves selected public Git objects from 58 captured refs in
Expand Down
40 changes: 40 additions & 0 deletions STATUS.md
Original file line number Diff line number Diff line change
Expand Up @@ -149,6 +149,46 @@ receipt or site outcome. The full Layer A, G0–G11, no-skip regression,
current pins and cold-start criteria remain open; neither CBZ-0 nor terminal
Partial is established. No scientific or proof status changes here.

## Selected historical text custody candidate — observed 10 November 2026

This candidate preserves exact Git head/tree objects and selected changed
head-side text blobs from 430 historical public Main and Math refs: 588 Main
`.lean` blobs and 608 Math `.lean`/`.md` blobs, with 6,867 head/path bindings.
The case-sensitive suffix selection, separately observed defaults, exact
identities and exclusions are in the [custody record](cbz/evidence/public-selected-text-custody-20261110/README.md). It does not
preserve deleted default-side blobs, unchanged files, other suffixes, Gitlink
contents or private refs. Ref currency, semantic uniqueness, proof status,
logical isolation and scientific acceptance are not inferred. No ref is
removed.

A fresh copy of the packaged record checked all 24 checksums, completed four
Main/Math cold readbacks in normal and optimized Python modes, and ran the
specified adverse driver: two clean passes, 30 altered-selection or source
record rejections, four detected verifier-mutant executions and two damaged-pack
rejections. These are bounded source-custody controls, not a complete Layer A
auditor, proof inventory or final G0/G10 gate.

From the Main checkout, run these exact source-custody checks in a disposable
directory with Git and Python's standard library:

```sh
CBZ_TEXT_CHECK_DIR=$(mktemp -d) || exit 1
cp -a cbz/evidence/public-selected-text-custody-20261110 "$CBZ_TEXT_CHECK_DIR/text-custody" || exit 1
cd "$CBZ_TEXT_CHECK_DIR/text-custody" || exit 1
sha256sum -c SHA256SUMS || exit 1
python3 -B -S cold_restore_captured_text_blobs.py main || exit 1
python3 -B -S cold_restore_captured_text_blobs.py Math- || exit 1
python3 -B -S test_captured_text_blobs_adverse.py || exit 1
```

Separately, Main #796 merged at `812a799f4cf4cee730efa0177a9101af4cf259ef`;
Workspace #68 merged at `83f14fda7ad9acf6b35a642b3e9e6a18e60912de` and its
post-merge eight-pin check observed Main `812a799f` and Math `9bdfc54b`.
Main #798 was a ready source-custody candidate at head `0a5b9eca` at the
subsequent read. Its navigation artifact recorded 2,686 tests with 24 explicit
skips. These observations were separate and can become stale; they do not
establish a current consistent federation cut or complete regression.

## Public branch custody candidate — observed 10 November 2026, 02:19 UTC

This candidate preserves selected public Git objects from 58 captured refs in
Expand Down
37 changes: 37 additions & 0 deletions TOOLING.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,6 +72,43 @@ These checks do not prove an authenticated Pages status is available or that a
real dispatch succeeded; reads and external actor state are not atomic. They
are not a full tool audit, final G0 or mathematical certification.

## Selected historical text custody readback — 10 November 2026

**Purpose and scope.** Independently replay captured Git tree comparisons,
reselect the stated suffixes, and read the selected blob packs by Git SHA-1
and SHA-256. Git and Python's standard library are required.

This candidate preserves exact Git head/tree objects and selected changed
head-side text blobs from 430 historical public Main and Math refs: 588 Main
`.lean` blobs and 608 Math `.lean`/`.md` blobs, with 6,867 head/path bindings.
The case-sensitive suffix selection, separately observed defaults, exact
identities and exclusions are in the [custody record](cbz/evidence/public-selected-text-custody-20261110/README.md). It does not
preserve deleted default-side blobs, unchanged files, other suffixes, Gitlink
contents or private refs. Ref currency, semantic uniqueness, proof status,
logical isolation and scientific acceptance are not inferred. No ref is
removed.

**Exact command.** From a Main checkout:

```sh
CBZ_TEXT_CHECK_DIR=$(mktemp -d) || exit 1
cp -a cbz/evidence/public-selected-text-custody-20261110 "$CBZ_TEXT_CHECK_DIR/text-custody" || exit 1
cd "$CBZ_TEXT_CHECK_DIR/text-custody" || exit 1
sha256sum -c SHA256SUMS || exit 1
python3 -B -S cold_restore_captured_text_blobs.py main || exit 1
python3 -B -S cold_restore_captured_text_blobs.py Math- || exit 1
python3 -B -S test_captured_text_blobs_adverse.py || exit 1
```

**Observed verification and limits.**

A fresh copy of the packaged record checked all 24 checksums, completed four
Main/Math cold readbacks in normal and optimized Python modes, and ran the
specified adverse driver: two clean passes, 30 altered-selection or source
record rejections, four detected verifier-mutant executions and two damaged-pack
rejections. These are bounded source-custody controls, not a complete Layer A
auditor, proof inventory or final G0/G10 gate.

## Public branch custody readbacks — 10 November 2026

**Purpose and scope.** Compare captured public head tree/path identities to a
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# Architecture preparation failure: bounded artifact readback

The failed Main #800 architecture job `129615470742`, run `42751353078`, checked merge `b269dba8e17e082395a46a90ef60b3a609c64921`. It reported `SETUP_BLOCKED`, 40 available originals and `recovery_complete: false`. Its retained 43-file artifact is `13734016279`, with reported ZIP SHA-256 `bbb826252a0385ae9427e05353c9fbffa55265d91e351536eef365a1678d3d1e`.

The separate read-only hosted diagnostic run `42751819416`, job `129616953406`, workflow source commit `9565e46330b1540d70aca0ed14f222540c70f395`, actually downloaded that ZIP, verified its digest and unique bounded result member, and checked the native run/merge identities. It reported `preparation_error = ValueError: unsafe/private daemon config refuses mutation`, `recovery_error = null`, `daemon_mutation_completed = false`, and `source_and_test_exposed = true`. This is a scoped inspection of one failure; it does not validate the architecture stage, prove all archive members, establish daemon state outside the reported observation, or qualify a CBZ gate. The diagnostic is not a general artifact certifier.

The separate public-intake job `129615465721` on the same head failed because its PR base was not Main. Its observed failure is preserved; retargeting and an actual successful run are required. The three files ending `.log` are decoded hosted job logs, not claims of byte-for-byte raw archive identity. The diagnostic workflow is retained as historical source; it is not an active workflow in this candidate tree. No private daemon configuration is reproduced here.
Loading
Loading