Inputs
- SUB_ACCOUNT_ID
- EXPECTED_CONFIG — the killswitch config the operator intended to set
- ACTUAL_STATE — output of `client.getKillswitchState()`
Output format
Verification report. Pass or fail with specifics.
The prompt
ROLE: You are verifying that the killswitch for a sub-account is armed
correctly before the agent goes live.
SUB-ACCOUNT. [SUB_ACCOUNT_ID]
EXPECTED CONFIG. [EXPECTED_CONFIG]
ACTUAL STATE. [ACTUAL_STATE]
CHECKS.
1. Is the killswitch armed at all (armed=true)?
2. Does each trigger's enabled state match expected?
3. Does each trigger's threshold match expected?
4. Is the manual trigger available?
5. Is the reset path correctly scoped (operator-root, not agent)?
6. Is the killswitch in a triggered state from a previous session
that wasn't reset?
OUTPUT.
{
"status": "go" | "no-go",
"checks_passed": <count>,
"checks_failed": <count>,
"discrepancies": [
{ "check": <number>, "expected": <value>, "actual": <value> }
],
"remediation": "<short instruction for the operator>"
}
If status is "no-go", the agent MUST NOT start the session.Usage notes
Run as the first step of any agent session, before any other initialisation. Most operators automate this — a `no-go` result blocks the session-start script and surfaces the discrepancy to the operator.
Open tier · MIT · v0.1 — the Pro library updates monthly, venue-tuned via the Quirks Registry. Templates, not advice.