Record Whitehat T03 acceptance dispositions under T07

Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a102c2-7bb6-71d1-b3bc-991a9074c0e6
This commit is contained in:
tegwick 2026-10-03 19:18:22 +02:00
parent 681144e5d4
commit 19e7feb3cb
3 changed files with 147 additions and 0 deletions

View file

@ -0,0 +1,98 @@
# WHITEHAT-WP-0009-T03 acceptance dispositions
Date: 2026-10-03. Acceptance owner: EMERGENT-WP-0002-T07.
Request: `whitehat-security/o`, correlation `WHITEHAT-WP-0009-T03`.
Requirements and Whitehat evidence reviewed at whitehat-security commit
`6793629`: `workplans/WHITEHAT-WP-0009-emergent-knowledge-offline-review.md`,
`evidence/2026-10-03-emergent-021-offline-review.md` and `.json`, and
`evidence/2026-10-03-emergent-023-offline-retest.md` and `.json`.
Target release: **0.2.3**, digest
`60f8811c6b94b30d357a0d9e5022f2a8ea52e69b47138d3a536755f3295310b5`,
implementation/retest commit `681144e5d4f59ef00418e7ae776e180b671f5d4d`.
This record changes acceptance evidence only, not the release or source pins.
## 1. Independence — accepted for the scoped repository review
The separately authored Whitehat probes and retained-scenario review meet
T07's request to seek a **whitehat-security-owned offline adversarial review**.
T07 does not require a separately authenticated principal for that scoped
repository review. This accepts the disclosed limits, not a stronger claim:
the original reviewer shares the implementing parent session, model family,
workspace and organizational context; the later retest is also a
Whitehat-scoped repository worker, not an authenticated independent principal.
Neither report establishes external independence, institutional assent,
human adoption, live assurance, or full T07 acceptance. Implementer tests
remain distinct evidence and do not become independent tests by this decision.
## 2. Library findings — remediation accepted for the named digest
**WH-KNOW-001 / RISK-F-0013:** accept remediation of post-load unsealed card
content. Whitehat's 0.2.3 retest records `release content changed; review and
reseal`, no returned card bytes, and no synthetic unsealed content returned.
**WH-KNOW-002 / RISK-F-0014:** accept remediation of the loaded lifecycle
snapshot. Whitehat's retest records `release changed; reload the reviewed
bundle` after withdrawal/reseal, no returned content, and withholding on a
fresh object.
The original 0.2.1 reproducer still reports both findings; the 0.2.3 retest
reports nine bounded passes, with known-bad rejected and known-good accepted
by each oracle. The implementing regression evidence in
[the 0.2.2 repair record](2026-10-03-owner-reviews-and-022-fixes.md) remains
separate from Whitehat's retest. Today's implementing knowledge suite passes
38 tests. Acceptance is limited to these library defects on this exact digest;
it does not prove a universal tenant or runtime boundary. No risk register
status or severity is changed here; risk-nexus owns those records.
## 3. Provider renewal — waiting; RISK-F-0015 remains open
Current-release provider evidence has not been renewed. The source-validated
0.2.3 `start` retrieval is **withheld** because an inventoried Informed Decision
source differs from the seal. The findings card retrieves as `verified-files`,
but that does not establish a usable current-source startup path. Existing
provider tools are installed; their presence is not successful session evidence.
No provider invocation or new credential acquisition was performed for this
record. An instrumented offline snapshot probe would not repair this
current-source gate or prove supported session continuity.
The 0.2.2 Codex/Claude reports retain their original digest and cannot count
toward 0.2.3 T05/T07 acceptance. **RISK-F-0015 remains open**, including both
Claude `model-switch` and `zones` routing. After source reconciliation and any
reviewed new seal, T05/T07 require fresh exact-release provider reports, semantic
review of the actual next recipients for both cases, and the existing
continuity/harness requirements. Missing model/session facts remain unknown;
no provider success or institutional assent is inferred.
## 4. Informed Decision drift — retain pin; reconciliation waiting
Retain seal pin `f0c60637e3fe592a23cc31ace8e4d386ff04b710`. Whitehat observed
dirty sibling HEAD `c1a75e85aa1c15ca0e09980e04ea2970b377659b`; today's read-only
check observed HEAD `c8e99c974a4766f2ed97a398e70835e838de47df` with a modified
ad hoc workplan and untracked provisioning artifacts. This later observation
does not alter Whitehat's historical receipt. The inventoried
`workplans/INFD-WP-0005-frictionless-decision-intake.md` differs from the pin;
HEAD movement alone is not the source-check criterion.
[Today's source receipt](2026-10-03-whitehat-t03-source-check.json) records
23 owners `verified-files`, `informed-decision: changed`, `ok: false`, and
`live_state_verified: false`. The 0.2.3 seal check passes. The earlier
[0.2.3 re-pin receipt](2026-10-03-023-source-repin.md) remains historical;
its all-verified result does not describe today's sibling files.
Do not re-pin or reseal from the dirty checkout. Await owner-published source
provenance, then review the committed inventoried changes under T04's freshness
contract before any new pin/release and exact-release provider renewal. This
dependency remains live in T07 with T05; T04's implemented freshness mechanism
is not undone by its correct detection of later drift. No sibling files,
adoption packet, provider results, credentials or operational controls changed.
## Task disposition
T07 remains **wait**: the bounded offline review and two library fixes are
accepted; source reconciliation, current-release provider routing/validation
and remaining continuity/harness evidence are still required. T05, T08, T09,
T10 remain **wait**, T02's human adoption gate remains open, and the workplan
remains **blocked**. Whitehat owns its T03 status; this record neither edits
that task nor closes risk-nexus findings. No packet or coordination message
was sent. The four dispositions are recorded in this repository only.

View file

@ -0,0 +1,33 @@
{
"schema": "emergent.knowledge-check.v1",
"version": "0.2.3",
"package_digest": "60f8811c6b94b30d357a0d9e5022f2a8ea52e69b47138d3a536755f3295310b5",
"sources": {
"net-kingdom": "verified-files",
"gate-house": "verified-files",
"ops-warden": "verified-files",
"ops-mason": "verified-files",
"access-engine": "verified-files",
"security-canon": "verified-files",
"user-engine": "verified-files",
"tenant-engine": "verified-files",
"zone-engine": "verified-files",
"whitehat-security": "verified-files",
"kings-guard": "verified-files",
"secrets-engine": "verified-files",
"key-cape": "verified-files",
"approval-engine": "verified-files",
"informed-decision": "changed",
"audit-core": "verified-files",
"risk-nexus": "verified-files",
"info-tech-canon": "verified-files",
"ops-bridge": "verified-files",
"railiance-master": "verified-files",
"glas-harness": "verified-files",
"the-custodian": "verified-files",
"emergent-security": "verified-files",
"runbook-tutorials": "verified-files"
},
"live_state_verified": false,
"ok": false
}

View file

@ -295,6 +295,22 @@ invented permission; any unsafe action recommendation blocks release. Record
all results and rerun failed cases after fixes. Seek whitehat-security-owned
adversarial review; fixture evaluation does not authorize live attack traffic.
**Acceptance disposition — 2026-10-03, WHITEHAT-WP-0009-T03:**
[Four dispositions](../docs/evidence/2026-10-03-whitehat-t03-dispositions.md)
accept the disclosed shared-session limits for the requested Whitehat-owned
offline repository review and accept remediation of WH-KNOW-001/RISK-F-0013
and WH-KNOW-002/RISK-F-0014 on 0.2.3 digest `60f8811c` at `681144e5`.
Implementer regressions and Whitehat retest remain separate evidence; no
authenticated independent principal, institutional assent or live assurance
is claimed. RISK-F-0015 (Claude model-switch and zones routing) remains open.
Current-release provider renewal waits: today's source check reports
`informed-decision: changed`, and source-validated startup is withheld. Retain
pin `f0c60637`; do not refresh from dirty sibling files. Await owner-published
source provenance and reviewed reconciliation, then renew exact-release
provider/routing and continuity/harness evidence under T05/T07. T07 stays
`wait`; T02/T05/T08/T09/T10 and the blocked plan status remain unchanged.
Risk register and Whitehat task statuses belong to their owners.
## T08 — Pilot in representative ecosystem repositories
```task