Implement source-backed NetKingdom agent security knowledge pilot

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

View file

@ -0,0 +1,18 @@
# Claude entry point
Owner-installed CLAUDE.md pointer (or supported AGENTS.md configuration):
Before security-related work, read the trusted package's `cards/start.md` and
retrieve the task's card. With the package installed, run
`emergent-knowledge show start --audience claude`, followed by
`emergent-knowledge show <card> --audience claude`.
Use `--repositories <checkout-parent>` before `show` to check source freshness.
Record version, digest, source state, resolved scope and missing facts. Reload on
resume/compaction and repo change. This is orientation, never a grant.
A CLAUDE.md import may load the startup card directly when the bundle is placed
inside the approved workspace: `@path/to/bundle/cards/start.md`. Do not silently
import arbitrary external paths or assume every version loads AGENTS.md. Verify
actual discovery and task-specific reading in a fresh session. The common card
owns the knowledge; this adapter owns only loading. Explicit rendered context is
the fallback, recorded as `explicit-bootstrap`.

View file

@ -0,0 +1,17 @@
# Codex entry point
Owner-installed AGENTS.md pointer:
Before security-related work, read the trusted Emergent Security package's
`cards/start.md`; retrieve the card for the task. With the package installed,
run `emergent-knowledge show start --audience codex`, then
`emergent-knowledge show <card> --audience codex`.
Use `--repositories <checkout-parent>` before `show` to check current source
files. Omission is explicitly offline. Record version, digest, source state,
resolved scope and missing facts. Repeat on resume/compaction or repo change.
Unknown scope is a question; a knowledge receipt is not authority.
AGENTS.md discovery depends on the actual session root and instruction settings.
Confirm the pointer was loaded in a fresh session. A pointer alone is not evidence
that its target was read. If instruction discovery is unavailable, provide the
same rendered context explicitly and label that mode `explicit-bootstrap`.

View file

@ -0,0 +1,15 @@
# New agent or harness entry point
The provider-independent interface is `emergent.knowledge-receipt.v1` from
`emergent-knowledge show <card> --audience generic --json`.
Load `start` first, then the task's card. Refuse a withheld result. Present
offline-snapshot status alongside the text, never just the cached content.
Record package version/digest, card, source statuses, and loading mode, without
credentials or private tenant/task contents. The receipt omits task context on
purpose; resolve scope in the authorized session, not in a shared knowledge log.
After context reset, resume or repository switch, load again. A harness adapter
may pass this rendered content through its supported context input; it must not
change model routes, sandbox settings, grants or tool policy. Test startup,
deeper retrieval, source drift, unknown scope and an unsafe-action scenario.
Only mark a surface supported after the real session demonstrates them.

View file

@ -0,0 +1,17 @@
# Grok entry point
Owner-installed AGENTS.md/CLAUDE.md pointer for the verified Grok Build session:
Read the trusted package's `cards/start.md`, then retrieve the task's card.
With the package installed, run
`emergent-knowledge show start --audience grok`, followed by
`emergent-knowledge show <card> --audience grok`.
Use `--repositories <checkout-parent>` before `show` for source checks. Record
version, digest, source state, resolved scope and missing facts; reload after
resume/compaction and repo change. Context never authorizes an effect.
Verify the actual installed Grok Build instruction discovery; the Grok web
product is a different surface. Where file loading is unavailable, pass the
rendered package using the client's explicit prompt interface and record
`explicit-bootstrap`. Never imply that adding a prompt configures permissions,
enforces isolation, or supplies credentials. Preserve the configured model route.