emergent-security/knowledge/cards/runbooks.md
tegwick 445179edfa Link security knowledge to human decisions and guided runbooks
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a101af-e240-7882-a1e3-e37720cbdbea
2026-10-03 15:50:04 +02:00

43 lines
2.7 KiB
Markdown

# Guided procedures and evidence
`runbook-tutorials` owns the pack schema, validator, engine and local UI.
The procedure owner keeps operational packs under its own `runbooks/` directory:
net-kingdom for its bootstrap procedures, ops-warden for access routing, and
other owners for their own effects. Emergent Security owns only its orientation
and rehearsal pack. Discover a specific pack from its owner; a cross-repository
pack index and automatic step execution remain RBT-WP-0006 work.
Route questions about engine auto-confirm behavior to runbook-tutorials. Route
claims that a waiver or rehearsal seal satisfies a protected effect to that
effect owner/PEP for verification against its actual prerequisites. Ask the
delegator only for unresolved task scope or an outstanding human decision.
Read the actual pack and scripts before running or verifying them. Resolve
actor, tenant, environment, target, current pack digest, knowledge release,
applicable human decisions and effect-owner prerequisites. Schema validity and
maturity are evidence of a procedure, not an access grant. Pack `actors`,
`privileges`, `authorized_by`, confirmation text and local waivers are descriptive
or operator-supplied records; they are not authenticated approval-engine facts.
Prefer manual mode for security handoffs. Auto-confirm never runs a step's own
command, but it CAN run verification commands and auto-confirm manual checks.
Treat verification commands as code with their own effect scope. Auto-confirm,
waivers, overrides, push-through and timeouts cannot discharge a required human
decision or authorization gate. Keep a human decision in informed-decision and
verify the owner's current approval/PDP contract before any protected effect.
The engine's generic waivers must not be mistaken for permission to bypass it.
Capture non-secret references, not credentials, tenant packet content, bearer
material or raw command dumps. Secret-marker scanning is incomplete. A local
sealed run is a content checksum, not signed identity, independent custody or
proof of authorization; someone controlling the file can also recompute it.
A succeeded run is limited by its actual checks, environment and pack revision.
Record deviations and unavailable evidence; never relabel them as success or
promote rehearsal maturity into production assurance.
On source/pack changes, resume or scope changes, reload knowledge and recheck
prerequisites. Route decision uncertainty to the human/delegator via
informed-decision; procedure defects to the pack owner; engine defects to
runbook-tutorials; security findings to risk-nexus and the defect owner.
Source owner IDs: `runbook-tutorials`, `informed-decision`, `approval-engine`, `access-engine`, `audit-core`, `net-kingdom`.