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

Implement source-backed NetKingdom agent security knowledge pilot

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a101af-e240-7882-a1e3-e37720cbdbea
This commit is contained in:
tegwick 2026-10-03 15:25:04 +02:00
parent caa7da2397
commit a835c11ae7
54 changed files with 3634 additions and 27 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -4,7 +4,7 @@ type: workplan
title: "Agent security knowledge and NetKingdom integration"
domain: communication
repo: emergent-security
status: ready
status: active
owner: codex
topic_slug: netkingdom
created: "2026-10-03"
@ -123,7 +123,7 @@ as explicit decisions with owners; do not silently pick the more permissive text
```task
id: EMERGENT-WP-0002-T01
title: Establish authoritative sources and current capabilities
status: todo
status: done
priority: high
state_hub_task_id: "803a1a79-e18a-5c1a-8722-be87bade7498"
```
@ -147,7 +147,7 @@ and link it rather than opening duplicate implementation plans.
```task
id: EMERGENT-WP-0002-T02
title: Reconcile doctrine and the reference evaluator boundary
status: todo
status: progress
priority: high
state_hub_task_id: "f6b17f12-d5b0-586c-bb2a-499c566d311e"
```
@ -172,7 +172,7 @@ Unsettled conflicts block the affected knowledge from normative distribution.
```task
id: EMERGENT-WP-0002-T03
title: Build source-backed security knowledge for agent sessions
status: todo
status: done
priority: high
state_hub_task_id: "8fb372ce-02d7-5c7a-9ac6-1cd0bdb1a006"
```
@ -200,7 +200,7 @@ conflicts are resolved and its context cost is measured.
```task
id: EMERGENT-WP-0002-T04
title: Make knowledge retrieval scoped versioned and refreshable
status: todo
status: done
priority: high
state_hub_task_id: "91bcefcb-0caf-5f3a-b8f7-07e3920b7856"
```
@ -223,7 +223,7 @@ data, not a new delegator or permission channel.
```task
id: EMERGENT-WP-0002-T05
title: Integrate and verify provider-specific knowledge loading
status: todo
status: progress
priority: high
state_hub_task_id: "012355d7-86c4-59dc-9a5c-85f4ced5a898"
```
@ -249,7 +249,7 @@ conflates knowledge loading with isolation/enforcement readiness.
```task
id: EMERGENT-WP-0002-T06
title: Connect delegation knowledge to owned operational interfaces
status: todo
status: done
priority: high
state_hub_task_id: "e71284b9-9e2d-53cb-be6b-a9424c7972a5"
```
@ -274,7 +274,7 @@ silently take over their implementation or publish their assent.
```task
id: EMERGENT-WP-0002-T07
title: Test situational understanding and unsafe routing failures
status: todo
status: progress
priority: high
state_hub_task_id: "9cc74076-4143-58d6-8791-fca0f34f430d"
```
@ -300,7 +300,7 @@ adversarial review; fixture evaluation does not authorize live attack traffic.
```task
id: EMERGENT-WP-0002-T08
title: Pilot agent orientation across doctrine operations and engines
status: todo
status: progress
priority: high
state_hub_task_id: "6081755b-890c-51c7-a1ca-d4e062b7db5e"
```
@ -323,7 +323,7 @@ the preceding knowledge release. Capture owner feedback and link all defects.
```task
id: EMERGENT-WP-0002-T09
title: Roll out shared knowledge and establish update ownership
status: todo
status: progress
priority: medium
state_hub_task_id: "a92a8a62-ed4c-5720-9fa6-579ad811adcf"
```
@ -347,7 +347,7 @@ needs as owner work records, not buried prose or implied delivered capabilities.
```task
id: EMERGENT-WP-0002-T10
title: Verify adoption and hand off remaining owner work
status: todo
status: wait
priority: medium
state_hub_task_id: "9d43f76c-6a16-508d-8b4a-2a9c1b813c1e"
```
@ -362,3 +362,28 @@ DoD-Ok only when the completion contract is met. Every residual has a linked
live work record and owner; unresolved safety-critical conflicts or missing
provider proofs keep this plan open. Sync the final source files through Repo
Manager and verify the primary Statehub projection matches the pushed commit.
## Implementation checkpoint — 2026-10-03
Local implementation is delivered as knowledge release **0.1.1 (pilot)**.
Source files, runtime CLI, package data, provider adapters, release/export and
pilot tooling, tests, and evidence are in this repository. The full workplan
remains active; a local pilot is not the completion contract.
| Task | Evidence / remaining work |
| --- | --- |
| T01 done | `knowledge/sources.yaml`: 23 owners, 55 files, pinned revisions/digests; `docs/netkingdom-integration-map.md` records real capabilities and existing owner dependencies. |
| T02 progress | `docs/decisions/EMERGENT-DEC-2026-001-integration-profile.md` implements a local boundary and six dispositions. Owner ratification of broader adoption remains open; no policy or grant widened. |
| T03 done | 12 source-backed cards, catalog, 4,475-byte startup, source-specific citations. The non-normative profile may be piloted while T02 adoption remains open. |
| T04 done | Read-only CLI, lifecycle/freshness checks, safe offline snapshots, private-content refusal, sealed artifacts, export and reload. `tests/test_knowledge.py` covers failure paths. |
| T05 progress | Codex/Claude/Grok/generic adapters and actual provider probes. Actual compaction/resume and governed-harness evidence remain separate gaps; see provider reports. |
| T06 done | `docs/operational-contracts.md` maps requests, facts, decisions, approvals, credentials and evidence to actual owners; scenario corpus exercises the seams without a second PDP or live effects. |
| T07 progress | 20-case corpus, provider-envelope regression tests, semantic review and corrected provider runs. Independent whitehat-owned review and full Grok disposition remain explicit in evidence. |
| T08 progress | Eight thin pilot pointers in four actual repositories; four fresh Claude scenario reports and tested rollback. These are read-only comprehension pilots; broader owner feedback/adoption is pending. |
| T09 progress | `docs/knowledge-maintenance.md` defines refresh, publication, rollback and review triggers. No fleet broadcast or global config change. Owner publication/adoption and fleet reach remain open. |
| T10 wait | Completion evidence cannot be asserted until the provider, independent review, owner and rollout gates are met. Concrete review package: `docs/adoption-review.md`. |
Evidence index: `docs/evidence/2026-10-03-implementation.md`. The remaining work
is held by these live task IDs, not abandoned as prose. No DoD-Ok is claimed for
EMERGENT-WP-0002, and no outside owner assent has been fabricated.