T08: .claude/rules/worker-protocol.md (imported by CLAUDE.md, pointed to from AGENTS.md) and tools/contract-tests/excerpt.py: name the rows, hand every worker one excerpt, one owner per step, check with the excerpt's tests. A test requires every table row to have details and a contract test (found O4). T06: bounded-executor/window_watch.py flags or closes the write role when no run Job is active or recent; stub tests; in the image. Built from the excerpt for O5, E1, C1, E8, E9, R2. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 943911@bnt-lap001 Assistant-Session: fc322940-1c8e-4bed-ab39-86cec99f23a0
2.5 KiB
NetKingdom — Claude Code Instructions
@SCOPE.md @.claude/rules/repo-identity.md @.claude/rules/session-protocol.md @.claude/rules/first-session.md @.claude/rules/workplan-convention.md @.claude/rules/stack-and-commands.md @.claude/rules/architecture.md @.claude/rules/repo-boundary.md @.claude/rules/credential-routing.md @.claude/rules/agents.md @.claude/rules/worker-protocol.md
NetKingdom situational knowledge pilot
For security-related work, read the shared Emergent Security orientation and the task's card in that package. From this repository root, validate and read:
PYTHONPATH=../emergent-security/src python3 -m emergent_security.knowledge --repositories .. show start --audience generic
Use the matching provider audience when known and retrieve the relevant card.
Record package version, digest and source status; reload after resume/compaction
or a repository switch. A withheld card requires source review; an offline
snapshot is orientation only. If the sibling checkout is absent, use the trusted
installed emergent-knowledge package or an explicitly reviewed exported bundle;
do not silently download or execute a replacement.
This pilot adds situational knowledge, not authority, live readiness or a change
to this repository's owner contracts. Work: emergent-security/EMERGENT-WP-0002.
Security quickstart for agents (Claude Code, Codex, Grok)
- Find the tool:
make security-toolslists every security tool, the question it answers, how to run it and whether an agent may run it (tools/security-tools.jsonis the machine-readable form). Tool availability is not permission. - Know the rules:
SECURITY-COMPANION.mdsection 7 ("If you are an agent"). - Credentials:
warden route find "<need>" --json. Never ask for, print or store a secret value. - Accounts and accountable automation:
canon/standards/service-identity-privilege_v0.1.md, rules SI-14 (agents) and SI-15 (prepare, admit, execute, verify, retain). - Your effective authority is everything your tools can reach (SEC-DSM DSM-AGENT-008). Live changes, private keys and production credentials belong to the person: prepare and test on synthetic fixtures, and give them the exact command to run.
- Leave a trail: commits get assistant trailers from the hook; log State Hub progress with your agent name and session.