tegwick
ddc1337a63
Four repositories returned text reviews. Every substantive finding was about a rule that read as satisfied by a check that did not satisfy it, which is the failure mode this repo is structurally prone to: doctrine is graded on whether it is right and consumed on whether it is checkable, and only the implementers can tell those apart. GH-DEC-2026-010 — attribution is not identity. Obligation 1 said a PEP must hold a decision from access-engine; obligation 2 supplied a digest test emphatic that it was mechanical rather than a matter of judgement. That test establishes which request a decision is for and nothing about who issued it, and it cannot: every input to it is either sent by the caller or published, so a responder knowing a published package id and version returns a well-formed allow. Fail-closed protects against a decision point that is absent, not against one that lies. Section 9.4 required authenticated entries of the approval object and nothing required it of the decision, so obligation 5 was written over a pair a PEP could only half validate. The mechanism is access-engine's under section 17 and it is not the standard's to choose, so the condition is a declared section 13 gap rather than a rule invented here. Raised by access-engine against its own artifact, which had already recorded it as its own defect before reading our text. GH-DEC-2026-011 — ops-warden assented to GH-DEC-2026-009 on the falsifier's own terms, went looking for the section 5.1 escape hatch the reversal clause predicted, and reported it does not have one. Then it priced adoption: 0 of 3 signing targets and 3 of 21 routing lanes resolve to a zone, so the cell adopted today fails closed on nearly every certificate it issues whenever the engine is unreachable — including the continuity path an operator needs to repair that unreachability. Its ask for a dated transitional unknown: fail_open is declined; it is indistinguishable at runtime from the stance the rule forbids and would make the rule optional at the only moment it costs anything. Its second preference is adopted instead: 13.1 records a dated coverage figure beside each stance, so a strict consumer and an unclassified one stop reading alike. Coverage is disclosure and does not soften the stance — the record says so, and says what would make the column come out again. The round record is closed and carries the rest: totality by catch-all, absent versus unknown (closing the section 16 question this version opened), the drift test promoted to MUST, ops-mason marked, and approval-engine's four editorial-but-load-bearing findings. Its own finding ids are used rather than renumbered. kings-guard and audit-core did not return a review. Section 14 records that as not claimed rather than counting silence as assent, and names the sections that therefore carry no assent from the repository best placed to test them. Standard amended at net-kingdom@64394e9; it stays proposed, and publication and the acceptance flip are net-kingdom's. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012viPor8WJNCbV64ipwewrm Assistant: claude-code Assistant-Model: opus Assistant-Process: 1754332@bnt-lap001 Assistant-Session: 9c8ac536-ff5e-46a3-8ab1-a548bde25fc0 |
||
|---|---|---|
| .. | ||
| 2026-09-02-kings-guard-qonto-live-observation.md | ||
| 2026-09-02-secrets-engine-t06-candidate.md | ||
| 2026-09-02-whitehat-asm-fixture-calibrations.md | ||
| 2026-09-02-whitehat-asm-triage-review.md | ||
| 2026-09-02-whitehat-t06-fixture-return.md | ||
| 2026-09-06-v06-findings-audit.md | ||
| 2026-09-06-v08-assent-round.md | ||
| README.md | ||
Conformance review register
Gate House records doctrine dispositions for returned assurance and posture reports here. This directory does not hold raw exploit evidence, credential values, severity decisions, or another repository's remediation tasks.
Normative inputs:
A review record names the external report and safe evidence references, copies the executor's outcome without changing it, records Gate House's doctrine disposition, and links every residual to a live owner.
Returned reviews:
-
2026-09-02 — kings-guard qonto live observation: origin-linked advisory observation is staffed for one lane; load-bearing deny stream completeness remains unknown; doctrine dispositionno_change. -
2026-09-02 — Whitehat T-06 fixture return: fixture-class approval-replay resultpass; liveasm-t06remainspending/not_run; doctrine dispositionno_change.
Fixture-safe candidates and promotions:
2026-09-02 — secrets-engine T-06 approval-consumption candidate: promoted into Whitehat's fixture-only T-06 calibration; the live target remains pending.
Coordination reviews:
2026-09-02 — whitehat ASM triage review: all ten targets were triaged; Gate House accepted the class split and routes, and the T-06 reassessment produced the fixture return above.
Fixture calibration reviews:
2026-09-02 — Whitehat ASM T-01–T-10 fixture calibrations: all known-bad fixtures produce findings and known-good fixtures pass; live targets remainpending/not_run; doctrine dispositionno_change.
No live whitehat-security ASM execution report has returned under
conformance-reporting.v1. The live target set remains not_run, not
conformance.