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
18 changes: 17 additions & 1 deletion .github/workflows/current-site.yml
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ name: Current research site
- 'tools/node_status_refresh.py'
- 'tests/test_node_status_refresh.py'
- 'tests/test_node_status_freshness.py'
- 'tests/test_node_status_mutation_grader.py'
- 'cbz/evidence/node-status-freshness/run_mutations.py'
# inputs of the freshness suite and its mutation runner
- 'tools/validate_node_status.py'
Expand Down Expand Up @@ -49,6 +50,22 @@ jobs:
python3 -B -S -m unittest discover -s tests -p 'test_current_site*.py' -v
python3 -B -O -S -m unittest discover -s tests -p 'test_current_site*.py' -v
node --test tests/test_current_site.mjs
- name: Verify freshness mutation provenance
run: |
set -euo pipefail
mkdir -p "$RUNNER_TEMP/node-status-grader-evidence"
python3 -B -S -m unittest tests.test_node_status_mutation_grader -v > "$RUNNER_TEMP/node-status-grader-evidence/controls-normal.stdout" 2> "$RUNNER_TEMP/node-status-grader-evidence/controls-normal.stderr"
python3 -B -O -S -m unittest tests.test_node_status_mutation_grader -v > "$RUNNER_TEMP/node-status-grader-evidence/controls-optimized.stdout" 2> "$RUNNER_TEMP/node-status-grader-evidence/controls-optimized.stderr"
python3 -B -S cbz/evidence/node-status-freshness/run_mutations.py > "$RUNNER_TEMP/node-status-grader-evidence/mutations-normal.json" 2> "$RUNNER_TEMP/node-status-grader-evidence/mutations-normal.stderr"
python3 -B -O -S cbz/evidence/node-status-freshness/run_mutations.py > "$RUNNER_TEMP/node-status-grader-evidence/mutations-optimized.json" 2> "$RUNNER_TEMP/node-status-grader-evidence/mutations-optimized.stderr"
- name: Preserve freshness mutation evidence
if: always()
uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9
with:
name: node-status-grader-${{ github.run_id }}-${{ github.run_attempt }}
path: ${{ runner.temp }}/node-status-grader-evidence/
if-no-files-found: error
retention-days: 90

node-status-refresh:
# LANES-20261022 Lane 3: report-only freshness of records/node_status.
Expand All @@ -66,7 +83,6 @@ jobs:
run: |
python3 -B -S -m unittest tests.test_node_status_freshness tests.test_node_status_refresh -v
python3 -B -O -S -m unittest tests.test_node_status_freshness tests.test_node_status_refresh -v
python3 -B -S cbz/evidence/node-status-freshness/run_mutations.py > "$RUNNER_TEMP/node-status-mutations.json"
# Pull requests run only the offline steps above. The live refresh reads the GitHub API,
# so it runs on main pushes, schedules and manual dispatch, never on a pull request.
- name: Report-only freshness refresh (read-only GitHub API)
Expand Down
19 changes: 19 additions & 0 deletions BASELINE.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,25 @@ 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.

## Freshness provenance candidate — 9 November 2026

The sequential observed boundary is Main signed merge
`6ab126beda65e19865b8468b52f8757ac2324e1f`, Math-
`f532c3e2d91a0c7679a37c733741660917a9b21b`, and signed Workspace merge
`2441baf051312878ca28e462d455cfbcd8e91b20`, pinning that Main. Workspace
#53 passed its exact-head jobs and merged normally; four prior hosted runs
failed before jobs and are preserved. The post-merge pins job passed, while
the post-merge federation run failed before jobs with a GitHub internal
server error and its failed-job retry was refused with HTTP 403.
These sequential observations are not final G7; a later Main merge will again
require a guarded Workspace pin update. The isolated Main
freshness-grader repair and the precisely stale engineering record are
described in [STATUS.md](STATUS.md#freshness-provenance-repair-candidate--9-november-2026).
The old false mutation kill remains historical and cannot receive new
provenance credit. All twelve final criteria and a single current G0–G11
pass remain unawarded; neither CBZ-0 nor terminal Partial is established.
This section supersedes older dated descriptions of current tips below.

## Navigation history candidate — 9 November 2026

The sequential base is Main `5ebe5771d44160f56d4f2fd1e11726858d17dc90`,
Expand Down
3 changes: 3 additions & 0 deletions DECISIONS.md
Original file line number Diff line number Diff line change
Expand Up @@ -110,3 +110,6 @@ Append-only. Historical source outcomes remain in their original records.
| 2026-11-09 07:24 | 2 | B/tooling | Recoverably retired the final thirteen documented historical research/browser drivers that the current G11 graph did not execute. Exact native blobs remain recoverable; every plan, report, preserved failure, authorship record and product source remains unchanged. Fresh pre-change normal and optimized censuses were byte-identical and failed only on those thirteen tools. Exact deletion-tree censuses are byte-identical and pass with 69 tools, zero unresolved tools and zero production findings. The auditor passes 263/263 controls and kills 328/328 designated mutants per mode. Complete discovery passes 2,459 tests in each mode with 25 explicit skips; this does not award full-regression 100%. The G11 component is closed only for this exact candidate tree; final federation G11 and CBZ-0 remain unawarded pending current integration, pins, other gates, cold start and one-pass G0--G11. No theorem, proof, bound, axiom, kernel outcome, historical failure, authorship or scientific status changed. | Yes | Base signed Main `848cd66bbf4a73e77a6f3e1fff64ce4796150f6d`, tree `2f48833cbd051545be1a7d383137c99e5fa57a12`; deletion commit `26bd26594c6bf7d1678ae0ea40483b61e07fac61`, tree `473cd9a018993327536c6510ac78122eb830020f`; baseline/deletion census SHA-256 `5ce8979ff1b0ba1a5c77aaefcf276d135f4cc3d4314a4a00d9756cd3d2260342` / `793a7f09cdafb40b22283d284722a495628c22b707631ae0e887b10fb123adc6`; mutation receipt SHA-256 `e73ecb9f1a31208d4a92dfc5359e11ea8c6de833ab0df1495cc3c5675f05b97e`; full log SHA-256 `1cf4c2d78b85a7317e8e60e15a6fc382cc538950c6dc9ad65b57859c8a27a411` / `0d0122b4080e969d1d0795dde8a912d95c6aa2c52f3726999bb66fe261fee6d3`; durable v138 status/evidence SHA-256 `1f61a595a7bbbc0e4a3c661c3f860e0355c3fbe7db8c9d810ca42e25cff6f059` / `3af309a2ca2f951e5cca74f5647776822bb0de7459b0575ea0e9b486faae169c`. |
| 2026-11-09 08:24 | 2 | B/status | Bound all five canonical reading surfaces to the signed Main #777 / Workspace #51 serial integration boundary and independently read-back durable v139. The current Workspace gitlink exactly matches Main; the organization-visible open-PR search returned zero. Author-observed G11 component execution passes with 69 tools, zero unresolved or production findings, 263/263 controls and 328/328 designated mutant kills per mode. Complete discovery passes 2,459 tests per mode with 25 skips, so full-regression 100% remains false. Preserved the landed HTTP-504 failure on attempt 1 and successful targeted retry on the identical signed commit. No theorem, proof, quarantine, bound, axiom, authorship, failure, kernel outcome or scientific status changed; no independent review is invented and no CBZ criterion is awarded. A later Main merge requires another guarded Workspace pin refresh. | Yes | Main `ed5d83b7eff354cd7025117f4d2371422acd816b`, tree `87fdabafadfdb1ee2b766222b6d0c313de8d9a89`; Workspace `7019083126d3e9fb732447dee5c2895d8c5b7475`, tree `5d591958e516a582367deb4433cbedf300207d7d`; Math- `f532c3e2d91a0c7679a37c733741660917a9b21b`; durable v139 status/evidence SHA-256 `68c00bab7590630ddaae8f67e0d9e1dc081d5168bc65809b18cce5cf0518affc` / `02e6efe1360f2e2b93ea9c64687db14b6b610961ca93434d1527665461c0fbb0`; landed workflow `42581324023` attempts 1 and 2. |
| 2026-11-09 17:33 | 2 | B/regression | Require full Main history and a separate no-skip execution of the two historical reader-source classes in the navigation workflow. The previously landed 2,459-test log records 37 skips, including twelve missing-history events; it remains preserved. The candidate shell block passed 20/20 on an actual full clone and rejected an actual depth-one clone with twelve skips. Focused controls passed 25/25 per mode. Nine designated workflow mutations per mode produced intended selected-body failures, with explicit helper/nested/subject-origin refusal controls. Earlier summary-spoofing false acceptances and the initial non-discriminating probe attempt remain recorded; no future hosted outcome is inferred. The existing full discovery and historical test contract remain. No theorem, proof, bound, axiom, authorship, historical failure or scientific status changed; all final criteria remain unawarded. Reversible in native Git; any later Main merge requires a guarded Workspace pin refresh. | Yes | Main base `5ebe5771d44160f56d4f2fd1e11726858d17dc90`; Workspace `a3e6552104d89917105a668a296121680a7f03bc`; workflow SHA-256 `fde0aab9cd82c5709f7970da2d5935a7cbeea2f1559725b4639fd5ad23a6c641`; landed artifact `13660495414`, SHA-256 `b2b93e4a1792fef2c994559baee9852927ed26f3a00484cd301eee99de0e6f5a`; qualification archive SHA-256 `6fa1b43e564baa27270e311f44b56cd2e580b2564c8253805789ab17f4c39fcf`. |
| 2026-11-09 18:16 | 2 | B/tooling, conflict | Preserve the real subject-origin false kill in the older node-status freshness mutation grader and require actual pre-cleanup selected-body/assertion provenance for future kills. Add adverse and workflow controls, retain all eleven original mutations, and keep the strict stale outcome visible. Correct the `eng.hard-gate` status and published projection after the read-only directory observation while preserving its original source pin. Local tests and exact limits are in STATUS and TOOLING; hosted integration remains unobserved. This changes no mathematical or scientific disposition. | Yes | Native source `9486c850d0c22fd1438e18fb392dbe02d7bd214f`, tree `d9a794488b34168cad49580a40460b44a5b33dfd`; local qualification archive SHA-256 `9e980d03e16d94716d62df10c00a39c88f0c0717b9de414d60a13ebc5b3d7411`; [A8 finding](https://github.com/d6g8k5htny-coder/main/issues/738#issuecomment-6747450269); [source observation](https://github.com/d6g8k5htny-coder/main/issues/738#issuecomment-6747623136); [Workspace checks](https://github.com/d6g8k5htny-coder/main/issues/738#issuecomment-6747829645). |
| 2026-11-09 18:28 | 2 | B/integration, conflict | Integrated Workspace #53 through fresh exact-head checks and normal expected-head merge. The tested tree became signed Workspace `2441baf051312878ca28e462d455cfbcd8e91b20`, pinning then-current Main `6ab126be…`. Preserve the four earlier zero-job internal-server failures and refused retries. Main #782's actual provenance artifact qualifies the bounded hosted component, while navigation failed before jobs and two other workflow runs reported internal errors despite successful individual jobs. Preserve each outcome and require fresh current-head checks; no bypass or final-gate claim. | Yes | Workspace tested tree `13dd6b73201627177c568cb4233a33fb60acbbab`; hosted artifact SHA-256 `478e130f46398aa00756f4b78692a8a34e6897eda4d2ceb63bba43b74e71c303`; read-back supplement SHA-256 `528f5686c2ef37c214142d5d2ab00a2a4b8a5642aae320a5304002abbde464ce`; [board result](https://github.com/d6g8k5htny-coder/main/issues/738#issuecomment-6748069485). |
| 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`. |
17 changes: 17 additions & 0 deletions GOVERNANCE.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,23 @@ 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.

## Freshness mutation provenance candidate — 9 November 2026

An assertion is an admissible kill for the node-status freshness mutation
experiment only when the selected synchronous unittest case actually ran and
the pre-cleanup traceback identifies the selected body or explicitly captured
standard assertion code as the failure origin. Subject, helper, callback,
lifecycle, runtime, skip, malformed or incomplete outcomes do not qualify.
The prior grader's real subject-origin false kill remains recorded and its
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
fresh heads and normal required checks, preserving the recorded platform
failures. Older dated descriptions of current tips below are historical.

## Navigation history guard candidate — 9 November 2026

For history-backed reader checks, the navigation workflow must obtain the
Expand Down
14 changes: 14 additions & 0 deletions PROOF_INDEX.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,20 @@ 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.

## Freshness repair proof boundary — 9 November 2026

The candidate described in
[STATUS.md](STATUS.md#freshness-provenance-repair-candidate--9-november-2026)
changes an engineering mutation grader and a stale engineering record. It does
not change, close, refute or rebind any theorem, hypothesis, axiom, bound,
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.

## Navigation history candidate boundary — 9 November 2026

The candidate based on Main `5ebe5771d44160f56d4f2fd1e11726858d17dc90`
Expand Down
Loading
Loading