Security response and recovery
Keep proposal, human authorization, dispatch, application and independent verification separate.
Runtime scope
Review the exact proposal
A human administrator proposes a registered-agent quarantine against an open incident in the current project. The action expires between one minute and one hour from creation. The proposal's Idempotency-Key binds retries to its original incident, action, expiry and requester; changing the payload requires a new reviewed proposal.
A different current human administrator approves or rejects its exact revision. A source token, model, dispatcher or the requester cannot approve it. Changes in membership, tenant state, key scope, expiry or revision fail closed.
Durable response states
- REQUESTED: proposal only.
- AUTHORIZED: independent human approval is current.
- DISPATCHED: a dedicated worker holds a30second lease.
- ACKNOWLEDGED: enforcement accepted the leased command.
- APPLIED: the exact owned MC-1 quarantine exists; this alone is not verified containment.
- VERIFIED: a separate credentialed probe observed the actual access gate deny the target. Freshness and current-control checks still apply.
- RETRYING, FAILED, EXPIRED, CANCELLED and REJECTED preserve uncertainty and recovery boundaries.
Bounded dispatcher
Provide the exact HTTPS origin and a dedicated expiring security:dispatch credential through the secret store. It receives at most20 scoped jobs, performs fixed API calls and never receives arbitrary shell commands or URLs. It cannot verify its own action.
On an unknown outcome, reconcile the durable response after its lease expires. Do not bypass authorization or issue another approval. A quarantined control owned by another current action, or an existing revocation, remains intact.
node scripts/security-response-worker.mjs --onceCancellation and rollback
A current human administrator may cancel an unleased response or one with an expired worker lease, using its latest revision. The release operation removes only that response's exact quarantine ID; unrelated controls are preserved. Quarantine expiry is enforced by the established access gate.
Revoking the worker key stops subsequent effect commits through the database authority fence. Preserve incident, Trust and audit evidence when stopping a worker or rolling back an application deployment.
