Skip to content

fix(pptl): signed canonical audit reconstruction and verifier fail-closed handling - #1368

Draft
ndrorchestration wants to merge 2 commits into
mainfrom
fix/pptl-tgl-audit-reviewed-20261018
Draft

ndrorchestration wants to merge 2 commits into
mainfrom
fix/pptl-tgl-audit-reviewed-20261018

Conversation

@ndrorchestration

@ndrorchestration ndrorchestration commented Oct 18, 2026 •

Copy link
Copy Markdown
Owner

Current signed candidate — 2026-10-18

Head: 8a5e48a9e04d845f294324d71b673ef915af4d55 (GitHub-verified signature). Protected main and PR base remain 0e09ae555136fb9d433c7294f445e0b656c7e705.

  • First hosted failure, preserved: Python Tests & Quality Checks run 39171344162 on prior head 3c646d7... failed static checks in 3.10/3.11/3.12: six E302 and two E231 in two regression-test files.
  • Minimal signed remediation: commit 8a5e48a corrects only spacing around six tests and two lambda separators. Diff is restricted to pptl/tests/test_triadic_governance_loop.py and pptl/tests/test_v1_seal_verification.py. No runtime code, scientific record or authorization state changed.
  • Exact-head CI: fresh checks initiated for 8a5e48a; preserve distinctions between successful, failed and still-running workflows. Do not inherit prior-head greens.
  • Admission: DRAFT / HOLD / UNMERGED / NOT MERGE-AUTHORIZED. Complete hosted CI and eligible non-author technical review remain required. Scientific N=0; independent validation, canonical efficacy and High-Assurance remain unestablished/unauthorized.

Historical engineering record

Current signed candidate — October 18, 2026

  • Head: 8a5e48a9e04d845f294324d71b673ef915af4d55 (GitHub-verified signature), based on protected main 0e09ae555136fb9d433c7294f445e0b656c7e705.
  • Same-system CI correction: The first exact-head Python quality failure on 3c646d7... had six E302 and two E231 whitespace findings across two regression test files, repeated on Python 3.10/3.11/3.12. That first failure remains retained.
  • Correction commit: 8a5e48a adds blank-line spacing before six tests and corrects the two lambda whitespace separators. The update modifies only pptl/tests/test_triadic_governance_loop.py and pptl/tests/test_v1_seal_verification.py; no implementation/runtime or scientific artifacts are changed.
  • Fresh checks: Exact-head hosted workflows were initiated for 8a5e48a. Prior candidate checks do not transfer; the new head must be checked to terminal status before admission.
  • Disposition: DRAFT / HOLD / NOT MERGE-AUTHORIZED pending complete exact-head hosted verification and eligible non-author technical review of the entire canonical TGL repair. No independent scientific validation, freeze change, new authority, or efficacy claim.

Prior signed engineering lineage

Purpose

Signed current-main reconstruction of the canonical TGL acceptance repair from historical draft #1347, addressing #1343. Preserves original unsigned lineage as review history; no force-push or protected-main update.

Exact candidate

Commit 3c646d7, GitHub signature VALID, one parent 0e09ae5. Exactly five PPTL implementation/test paths. Source is the final October 18 staged correction reviewed in #1347, not the superseded October 16 export.

Requires complete canonical gate identity/order and coherent KILL prefix, premise PASS/KILL, actual submitted-input SHA-256 equality, and status reduction. Phi PASS with unwired HPG SKIP escalates. Verification/seal accessor exceptions reset TGL runtime and escalate rather than leaving EVALUATING.

Verification

Fresh Windows Python 3.12 PPTL: 204 passed. Staged diff whitespace check PASS. Same-system read-only source review found no critical/important regression. GitHub signature and single-parent main lineage verified.
Exact new-head hosted checks MUST be observed separately; old #1347 CI is not inherited. Historical broad Windows failures remain recorded on #1347, including failures reproduced on untouched main; no broad local all-green claim.

Admission and residuals

DRAFT / HOLD / NOT MERGE-AUTHORIZED pending exact-head hosted checks and eligible non-author review.
Issues #1366 (runner error event retention) and #1367 (same-input context replay design) remain separate. This change is not authenticated origin, nonce/context replay prevention, external exploit assessment, or independent scientific validation.
No freeze, preregistration, authorization, custody, analysis, scientific result or experimental artifact changes.
SCIENTIFIC_N_INCREMENT=0; INDEPENDENT_VALIDATION=NOT_ESTABLISHED; CANONICAL_DGAF_EFFICACY=NOT_ESTABLISHED; HIGH_ASSURANCE=NOT_AUTHORIZED.

Copy link
Copy Markdown
Owner Author

2026-10-18 exact-head QA closure — 8a5e48a (same-owner engineering only)

Confirmed: GitHub-reported fresh PR-triggered workflow runs at the signed exact commit 8a5e48a9e04d845f294324d71b673ef915af4d55: 23/23 completed SUCCESS, including the original Python Tests & Quality Checks failure lane across Python variants, Governance CI, PPTL CI, PDMAL Pre-Freeze Runner Validation and the PR Issue-State Keyword Guard rerun after the description reconciliation.

The original first-failure evidence remains available at Python quality run 39171344162 on earlier signed head 3c646d7.... It found six E302 and two E231 static-quality errors in two test files; these were repaired in a separate GitHub-verified signed commit 8a5e48a. That last commit contains only formatting changes in those two regression-test paths. No security assertion, canonical gate logic, runtime state, freeze, trial evidence, scientific output or authorization flag was modified by the formatting correction.

Acceptance boundary: exact-head CI is an engineering gate only. PR remains DRAFT / HOLD / UNMERGED, 0 eligible non-author reviews received, NOT MERGE-AUTHORIZED. An independent human technical review must inspect the full five-path canonical TGL repair, not merely the whitespace commit, and evaluate negative-case behavior, evidence identity, canonical status reduction, fail-closed verifier exceptions and the claim/authority boundaries before any admission decision. No external scientific validation or high assurance is implied. SCIENTIFIC_N_INCREMENT=0; INDEPENDENT_VALIDATION=NOT_ESTABLISHED; CANONICAL_DGAF_EFFICACY=NOT_ESTABLISHED; HIGH_ASSURANCE=NOT_AUTHORIZED.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant