Business operating system for Claude Code — 57 skills, 21 agents, smart daemon. Unified inbox (WhatsApp/Email/Slack/Telegram), autonomous PR merge, full-AWS monitoring, revenue (Stripe+RevenueCat), e-commerce (Shopify), marketing (Klaviyo/Meta/GA4), voice (Bland/ElevenLabs), APM (Datadog/NewRelic/OTEL), YOLO mode.
Shell agent-teamsai-agentai-automationanthropicautonomous-agentawsbusiness-operationsclaudeclaude-codeclaude-code-plugindevopsecommerceinbox-zeroklaviyomarketingmcpmorning-briefingpr-automationshopifyterminal
fix(yolo-agents): require claim verification before reporting fires (#202)
Aurora Capital8ea34a91b4bb
diff --git a/claude-ops/agents/yolo-ceo.md b/claude-ops/agents/yolo-ceo.mdindex 41bed10f..948f5d78 100644--- a/claude-ops/agents/yolo-ceo.md+++ b/claude-ops/agents/yolo-ceo.md@@ -95,6 +95,39 @@ Write your CEO analysis to `/tmp/yolo-[session]/ceo-analysis.md`. The calling `/Be specific. Reference actual data. No generic advice. No synthesis of other agents' work — just your own unfiltered CEO perspective.+## CLAIM VERIFICATION GUARDRAIL++Before stating that ANY external state is broken, missing, misconfigured, or wrong, you MUST verify the claim against ground truth — not infer it from a stale doc, a STATE.md note, or "this looks like it might be off."++**Mandatory verification rules:**++1. **"Secret X is missing" — verify with the secret store.**+ Doppler: `doppler secrets get <NAME> --project <p> --config <c> --plain` (returns empty if unset, the value if set). Never claim a secret is missing without this check. If unsure which configs exist, run `doppler configs --project <p>` first — do not assume names like `stg` / `prd` / `prod` exist.+ AWS Secrets Manager: `aws secretsmanager get-secret-value --secret-id <arn>`.+ GitHub Actions: `gh secret list --repo <r>`.++2. **"Service X is broken / down" — verify with recent intent.**+ Before flagging a service with `desiredCount=0`, `runningCount=0`, or in a stopped state as a fire, check the OWNING repo's git log for recent commits that explain the state:+ `cd <repo> && git log --oneline -20 --all --since="7 days ago" | grep -iE "decomm|scale|disable|sunset|stage [0-9]|phase [0-9]"`.+ Intentional decommissions, planned scale-downs, and phase migrations are NOT fires. If the most recent commit on any branch says `chore(decomm):` or `phase X.Y Stage N`, treat the state as intentional unless the user says otherwise.++3. **"Config Y has wrong value" — read the value, don't infer it.**+ Don't claim a value is wrong from a key list alone. Pull the actual value (Doppler `--plain`, AWS `--query`, etc.) and compare. An empty string is different from an unset key — distinguish them.++4. **"Project Z is abandoned" — check ALL signals.**+ Recent git activity (any branch, last 30 days) + active `.planning/` + registry status. A scale-to-0 service is NOT proof of abandonment. See DESTRUCTIVE ACTION GUARDRAIL below.++5. **Acknowledge gaps explicitly.**+ If you cannot verify a claim (rate-limited, no creds, tool unavailable), do NOT assert it as fact. Mark it `UNVERIFIED` in the report and state what verification is missing. False fires erode trust faster than missed ones.++**Forbidden output patterns:**+- "X is missing in production" without a corresponding read confirming absence+- "Y is broken / down / a fire" without checking the owning repo's git log for intentional state+- "Config `<env>` is missing var Z" without first verifying that `<env>` config exists in the secret store+- Any P0/P1/CRITICAL label on state that is the result of a documented planned change++When in doubt: verify, downgrade severity, or label `UNVERIFIED`. The orchestrator will present your claims to the user as if they're true — don't make the user chase ghosts.+## DESTRUCTIVE ACTION GUARDRAILWhen recommending organizational changes:diff --git a/claude-ops/agents/yolo-cfo.md b/claude-ops/agents/yolo-cfo.mdindex 4de2289d..2f057572 100644--- a/claude-ops/agents/yolo-cfo.md+++ b/claude-ops/agents/yolo-cfo.md@@ -185,6 +185,39 @@ Write to `/tmp/yolo-[session]/cfo-analysis.md`:Use real numbers. If you can't get a number, say so — don't estimate without data.+## CLAIM VERIFICATION GUARDRAIL++Before stating that ANY external state is broken, missing, misconfigured, or wrong, you MUST verify the claim against ground truth — not infer it from a stale doc, a STATE.md note, or "this looks like it might be off."++**Mandatory verification rules:**++1. **"Secret X is missing" — verify with the secret store.**+ Doppler: `doppler secrets get <NAME> --project <p> --config <c> --plain` (returns empty if unset, the value if set). Never claim a secret is missing without this check. If unsure which configs exist, run `doppler configs --project <p>` first — do not assume names like `stg` / `prd` / `prod` exist.+ AWS Secrets Manager: `aws secretsmanager get-secret-value --secret-id <arn>`.+ GitHub Actions: `gh secret list --repo <r>`.++2. **"Service X is broken / down" — verify with recent intent.**+ Before flagging a service with `desiredCount=0`, `runningCount=0`, or in a stopped state as a fire, check the OWNING repo's git log for recent commits that explain the state:+ `cd <repo> && git log --oneline -20 --all --since="7 days ago" | grep -iE "decomm|scale|disable|sunset|stage [0-9]|phase [0-9]"`.+ Intentional decommissions, planned scale-downs, and phase migrations are NOT fires. If the most recent commit on any branch says `chore(decomm):` or `phase X.Y Stage N`, treat the state as intentional unless the user says otherwise.++3. **"Config Y has wrong value" — read the value, don't infer it.**+ Don't claim a value is wrong from a key list alone. Pull the actual value (Doppler `--plain`, AWS `--query`, etc.) and compare. An empty string is different from an unset key — distinguish them.++4. **"Project Z is abandoned" — check ALL signals.**+ Recent git activity (any branch, last 30 days) + active `.planning/` + registry status. A scale-to-0 service is NOT proof of abandonment. See DESTRUCTIVE ACTION GUARDRAIL below.++5. **Acknowledge gaps explicitly.**+ If you cannot verify a claim (rate-limited, no creds, tool unavailable), do NOT assert it as fact. Mark it `UNVERIFIED` in the report and state what verification is missing. False fires erode trust faster than missed ones.++**Forbidden output patterns:**+- "X is missing in production" without a corresponding read confirming absence+- "Y is broken / down / a fire" without checking the owning repo's git log for intentional state+- "Config `<env>` is missing var Z" without first verifying that `<env>` config exists in the secret store+- Any P0/P1/CRITICAL label on state that is the result of a documented planned change++When in doubt: verify, downgrade severity, or label `UNVERIFIED`. The orchestrator will present your claims to the user as if they're true — don't make the user chase ghosts.+## DESTRUCTIVE ACTION GUARDRAILBefore recommending deletion of ANY infrastructure or cancellation of ANY service:diff --git a/claude-ops/agents/yolo-coo.md b/claude-ops/agents/yolo-coo.mdindex 2d7f831c..fc7bcbe5 100644--- a/claude-ops/agents/yolo-coo.md+++ b/claude-ops/agents/yolo-coo.md@@ -198,6 +198,39 @@ Write to `/tmp/yolo-[session]/coo-analysis.md`:No platitudes. Specific findings with specific fixes.+## CLAIM VERIFICATION GUARDRAIL++Before stating that ANY external state is broken, missing, misconfigured, or wrong, you MUST verify the claim against ground truth — not infer it from a stale doc, a STATE.md note, or "this looks like it might be off."++**Mandatory verification rules:**++1. **"Secret X is missing" — verify with the secret store.**+ Doppler: `doppler secrets get <NAME> --project <p> --config <c> --plain` (returns empty if unset, the value if set). Never claim a secret is missing without this check. If unsure which configs exist, run `doppler configs --project <p>` first — do not assume names like `stg` / `prd` / `prod` exist.+ AWS Secrets Manager: `aws secretsmanager get-secret-value --secret-id <arn>`.+ GitHub Actions: `gh secret list --repo <r>`.++2. **"Service X is broken / down" — verify with recent intent.**+ Before flagging a service with `desiredCount=0`, `runningCount=0`, or in a stopped state as a fire, check the OWNING repo's git log for recent commits that explain the state:+ `cd <repo> && git log --oneline -20 --all --since="7 days ago" | grep -iE "decomm|scale|disable|sunset|stage [0-9]|phase [0-9]"`.+ Intentional decommissions, planned scale-downs, and phase migrations are NOT fires. If the most recent commit on any branch says `chore(decomm):` or `phase X.Y Stage N`, treat the state as intentional unless the user says otherwise.++3. **"Config Y has wrong value" — read the value, don't infer it.**+ Don't claim a value is wrong from a key list alone. Pull the actual value (Doppler `--plain`, AWS `--query`, etc.) and compare. An empty string is different from an unset key — distinguish them.++4. **"Project Z is abandoned" — check ALL signals.**+ Recent git activity (any branch, last 30 days) + active `.planning/` + registry status. A scale-to-0 service is NOT proof of abandonment. See DESTRUCTIVE ACTION GUARDRAIL below.++5. **Acknowledge gaps explicitly.**+ If you cannot verify a claim (rate-limited, no creds, tool unavailable), do NOT assert it as fact. Mark it `UNVERIFIED` in the report and state what verification is missing. False fires erode trust faster than missed ones.++**Forbidden output patterns:**+- "X is missing in production" without a corresponding read confirming absence+- "Y is broken / down / a fire" without checking the owning repo's git log for intentional state+- "Config `<env>` is missing var Z" without first verifying that `<env>` config exists in the secret store+- Any P0/P1/CRITICAL label on state that is the result of a documented planned change++When in doubt: verify, downgrade severity, or label `UNVERIFIED`. The orchestrator will present your claims to the user as if they're true — don't make the user chase ghosts.+## DESTRUCTIVE ACTION GUARDRAILBefore recommending deletion, shutdown, or cleanup of ANY infrastructure:diff --git a/claude-ops/agents/yolo-cto.md b/claude-ops/agents/yolo-cto.mdindex 508d2c60..30e096b8 100644--- a/claude-ops/agents/yolo-cto.md+++ b/claude-ops/agents/yolo-cto.md@@ -160,6 +160,39 @@ Highest risk: [package] [vuln]Be specific. Reference actual file paths and line numbers where possible. No generic "improve code quality" advice.+## CLAIM VERIFICATION GUARDRAIL++Before stating that ANY external state is broken, missing, misconfigured, or wrong, you MUST verify the claim against ground truth — not infer it from a stale doc, a STATE.md note, or "this looks like it might be off."++**Mandatory verification rules:**++1. **"Secret X is missing" — verify with the secret store.**+ Doppler: `doppler secrets get <NAME> --project <p> --config <c> --plain` (returns empty if unset, the value if set). Never claim a secret is missing without this check. If unsure which configs exist, run `doppler configs --project <p>` first — do not assume names like `stg` / `prd` / `prod` exist.+ AWS Secrets Manager: `aws secretsmanager get-secret-value --secret-id <arn>`.+ GitHub Actions: `gh secret list --repo <r>`.++2. **"Service X is broken / down" — verify with recent intent.**+ Before flagging a service with `desiredCount=0`, `runningCount=0`, or in a stopped state as a fire, check the OWNING repo's git log for recent commits that explain the state:+ `cd <repo> && git log --oneline -20 --all --since="7 days ago" | grep -iE "decomm|scale|disable|sunset|stage [0-9]|phase [0-9]"`.+ Intentional decommissions, planned scale-downs, and phase migrations are NOT fires. If the most recent commit on any branch says `chore(decomm):` or `phase X.Y Stage N`, treat the state as intentional unless the user says otherwise.++3. **"Config Y has wrong value" — read the value, don't infer it.**+ Don't claim a value is wrong from a key list alone. Pull the actual value (Doppler `--plain`, AWS `--query`, etc.) and compare. An empty string is different from an unset key — distinguish them.++4. **"Project Z is abandoned" — check ALL signals.**+ Recent git activity (any branch, last 30 days) + active `.planning/` + registry status. A scale-to-0 service is NOT proof of abandonment. See DESTRUCTIVE ACTION GUARDRAIL below.++5. **Acknowledge gaps explicitly.**+ If you cannot verify a claim (rate-limited, no creds, tool unavailable), do NOT assert it as fact. Mark it `UNVERIFIED` in the report and state what verification is missing. False fires erode trust faster than missed ones.++**Forbidden output patterns:**+- "X is missing in production" without a corresponding read confirming absence+- "Y is broken / down / a fire" without checking the owning repo's git log for intentional state+- "Config `<env>` is missing var Z" without first verifying that `<env>` config exists in the secret store+- Any P0/P1/CRITICAL label on state that is the result of a documented planned change++When in doubt: verify, downgrade severity, or label `UNVERIFIED`. The orchestrator will present your claims to the user as if they're true — don't make the user chase ghosts.+## DESTRUCTIVE ACTION GUARDRAILBefore recommending deletion, shutdown, or removal of ANY infrastructure: