coulomb/emergent-security
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Bind knowledge retrieval to sealed bytes and invalidate changed releases

Browse source 
Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a10238-7ecc-78e2-903d-075f50e913cc
This commit is contained in:
tegwick 2026-10-03 17:44:52 +02:00
parent 416f9919c5
commit d0bf65e964
16 changed files with 335 additions and 40 deletions
Download patch file Download diff file Expand all files Collapse all files

43
workplans/EMERGENT-WP-0002-agent-security-knowledge-and-netkingdom-integration.md
View file

@ -499,3 +499,46 @@ fleet notice or human decision is authorized by this engagement. Scope remains
release 0.2.1 and its recorded digest; the plan returns to **active** while the
workers pursue the pending gates. T08/T10 remain waiting. The closure attempt
above is a historical checkpoint; no DoD-Ok is claimed by starting workers.
## Owner findings and consistency remediation — 2026-10-03
The owner workers delivered scoped doctrine, vocabulary, PDP-boundary and
session/distribution reviews. Gate House, NetKingdom and SecurityCanon found no
blocking documentary conflict; Access Engine technically accepts the orientation
boundary. Their original 0.2.1 pins, human/institutional limits and 0.2.2 renewal
conditions are retained. Publication and teaching roles have a concrete proposal,
not a human adoption or published fleet notice. Owner evidence/work-record IDs:
`docs/evidence/2026-10-03-owner-reviews-and-022-fixes.md`.
Whitehat's WHITEHAT-WP-0009 delivered WH-KNOW-001/002: post-load unsealed card
bytes and unobserved source withdrawal after reseal. **T04 was reopened for
remediation** within this existing plan. Five failing regressions reproduce the
binding/lifecycle gaps. Local implementation now revalidates the seal/package on
each operation, requires explicit reload after release changes, and returns the
exact hashed card bytes. **T04 implementation is done again:** 341 tests pass,
including nine real owner-contract checks; focused knowledge suite 38 passes.
Clean independent remediation acceptance remains part of T07, not inferred from
these implementing tests.
Corrected pilot **0.2.2**, digest
`19de26540c693b94ac8c19d7ed2ddd901acbc828c9b8a78b44c1a43ca468222c`.
The Glas owner fixed configured-model fallback and appended its contract. Our
source check detected that change, then the reviewed actual committed files were
re-pinned to `5ce4f38aedfd27cc783131f18480df02e2951514` before resealing. All
24 source owners verify as files. GLAS-WP-0008 is finished; GLAS-WP-0012 now holds
native provider/readiness/continuity evidence. CUST-WP-0073 holds distribution
and identity requirements. The unsigned adoption packet binds this exact release
and remains unsubmitted.
Whitehat's separate retained-Claude rubric scores 26/28 (zones capability-owner
routing plus model-switch recipient), compared with the earlier implementing
27/28; preserve both reviews and their limits. The Whitehat worker was stopped
by the platform cybersecurity-risk review after saving and delivering findings.
Its T03 close-out/sync and independence acceptance remain incomplete; do not
restart around the block or claim root regression tests close that review.
Workers continue provider diagnosis/current-release evidence, pilot feedback in
ops-warden/tenant-engine/railiance-master, and Informed Decision's actual attended
submission/admission requirements. Required gaps remain live in the original
T02/T05/T07/T08/T09/T10; no workplan completion or runtime authority is asserted.