thevoidforge-methodology 23.8.0 → 23.8.1

package/.claude/agents/silver-surfer-herald.md

@@ -78,9 +78,10 @@ TOTAL: [count]
 
 - **Hardcoded counts go stale.** Never cite a specific agent count in your output — say "all agents" or reference AGENT_CLASSIFICATION.md. (v23.7.0 lesson: 30+ files needed updating when one agent was added.)
 - **The command's hardcoded manifest is the floor, not the ceiling.** Your job is to add specialists the command didn't think to include. If the command already lists Kenobi for security, you don't need to add Kenobi — but you should add Worf, Tuvok, Ahsoka if the codebase warrants it.
+- **You MUST be launched. No exceptions.** The orchestrating agent (Opus) will be tempted to skip you when the task looks simple. "4 content-only missions" or "just a text fix" are NOT valid reasons to skip. You catch cross-domain relevance the orchestrator cannot predict from the task description alone. If you are not launched, the command violates protocol. (Field report: voidforge.build Campaign v14 — orchestrator admitted skipping the Surfer on a "simple" campaign, acknowledged it was a protocol violation.)
 
 ## Required Context
 
 - Agent definitions: `.claude/agents/*.md`
 - Agent classification: `docs/AGENT_CLASSIFICATION.md`
-- This agent is launched via `subagent_type: Silver Surfer` from every major command's Step 0.
+- This agent is launched via the Agent tool from every major command's Step 0. See any command file's "Silver Surfer Pre-Scan (ADR-048)" section for exact invocation parameters.

package/.claude/commands/ai.md

@@ -17,7 +17,9 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 ## Silver Surfer Pre-Scan (ADR-048)
 
-**MANDATORY.** Before deploying any domain agents, launch the Silver Surfer. **Do NOT skip this step.** Before launching, read the `## Cosmic Heraldings` section from `.claude/agents/silver-surfer-herald.md` and announce one at random (never repeat in the same session). Then launch the Surfer.
+**MANDATORY — NO EXCEPTIONS.** Launch the Silver Surfer before deploying ANY other agents. This is not negotiable, not deferrable, and not skippable regardless of how simple the task appears. "The task is simple" is NOT a valid reason to skip — the Surfer catches cross-domain relevance that you cannot predict. "I already know which agents to use" is NOT a valid reason — the Surfer reads agent definitions you haven't loaded. Skipping the Surfer is a protocol violation equivalent to skipping the Victory Gauntlet. **If you find yourself thinking "I don't need the Surfer for this" — that is exactly when you need it most.**
+
+Read the `heralding:` field from `.claude/agents/silver-surfer-herald.md` and announce it before launching.
 
 **How to launch:** Use the Agent tool with these exact parameters:
 - `description`: "Silver Surfer roster scan"

package/.claude/commands/architect.md

@@ -12,7 +12,9 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 ## Silver Surfer Pre-Scan (ADR-048)
 
-**MANDATORY.** Before deploying any domain agents, launch the Silver Surfer. **Do NOT skip this step.** Before launching, read the `## Cosmic Heraldings` section from `.claude/agents/silver-surfer-herald.md` and announce one at random (never repeat in the same session). Then launch the Surfer.
+**MANDATORY — NO EXCEPTIONS.** Launch the Silver Surfer before deploying ANY other agents. This is not negotiable, not deferrable, and not skippable regardless of how simple the task appears. "The task is simple" is NOT a valid reason to skip — the Surfer catches cross-domain relevance that you cannot predict. "I already know which agents to use" is NOT a valid reason — the Surfer reads agent definitions you haven't loaded. Skipping the Surfer is a protocol violation equivalent to skipping the Victory Gauntlet. **If you find yourself thinking "I don't need the Surfer for this" — that is exactly when you need it most.**
+
+Read the `heralding:` field from `.claude/agents/silver-surfer-herald.md` and announce it before launching.
 
 **How to launch:** Use the Agent tool with these exact parameters:
 - `description`: "Silver Surfer roster scan"

package/.claude/commands/assemble.md

@@ -15,7 +15,9 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 ## Silver Surfer Pre-Scan (ADR-048)
 
-**MANDATORY.** Before deploying any domain agents, launch the Silver Surfer. **Do NOT skip this step.** Before launching, read the `## Cosmic Heraldings` section from `.claude/agents/silver-surfer-herald.md` and announce one at random (never repeat in the same session). Then launch the Surfer.
+**MANDATORY — NO EXCEPTIONS.** Launch the Silver Surfer before deploying ANY other agents. This is not negotiable, not deferrable, and not skippable regardless of how simple the task appears. "The task is simple" is NOT a valid reason to skip — the Surfer catches cross-domain relevance that you cannot predict. "I already know which agents to use" is NOT a valid reason — the Surfer reads agent definitions you haven't loaded. Skipping the Surfer is a protocol violation equivalent to skipping the Victory Gauntlet. **If you find yourself thinking "I don't need the Surfer for this" — that is exactly when you need it most.**
+
+Read the `heralding:` field from `.claude/agents/silver-surfer-herald.md` and announce it before launching.
 
 **How to launch:** Use the Agent tool with these exact parameters:
 - `description`: "Silver Surfer roster scan"

package/.claude/commands/assess.md

@@ -4,7 +4,9 @@ Evaluate an existing codebase before a rebuild, migration, or VoidForge onboardi
 
 ## Silver Surfer Pre-Scan (ADR-048)
 
-**MANDATORY.** Before deploying any domain agents, launch the Silver Surfer. **Do NOT skip this step.** Before launching, read the `## Cosmic Heraldings` section from `.claude/agents/silver-surfer-herald.md` and announce one at random (never repeat in the same session). Then launch the Surfer.
+**MANDATORY — NO EXCEPTIONS.** Launch the Silver Surfer before deploying ANY other agents. This is not negotiable, not deferrable, and not skippable regardless of how simple the task appears. "The task is simple" is NOT a valid reason to skip — the Surfer catches cross-domain relevance that you cannot predict. "I already know which agents to use" is NOT a valid reason — the Surfer reads agent definitions you haven't loaded. Skipping the Surfer is a protocol violation equivalent to skipping the Victory Gauntlet. **If you find yourself thinking "I don't need the Surfer for this" — that is exactly when you need it most.**
+
+Read the `heralding:` field from `.claude/agents/silver-surfer-herald.md` and announce it before launching.
 
 **How to launch:** Use the Agent tool with these exact parameters:
 - `description`: "Silver Surfer roster scan"

package/.claude/commands/build.md

@@ -12,7 +12,9 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 ## Silver Surfer Pre-Scan (ADR-048)
 
-**MANDATORY.** Before deploying any domain agents, launch the Silver Surfer. **Do NOT skip this step.** Before launching, read the `## Cosmic Heraldings` section from `.claude/agents/silver-surfer-herald.md` and announce one at random (never repeat in the same session). Then launch the Surfer.
+**MANDATORY — NO EXCEPTIONS.** Launch the Silver Surfer before deploying ANY other agents. This is not negotiable, not deferrable, and not skippable regardless of how simple the task appears. "The task is simple" is NOT a valid reason to skip — the Surfer catches cross-domain relevance that you cannot predict. "I already know which agents to use" is NOT a valid reason — the Surfer reads agent definitions you haven't loaded. Skipping the Surfer is a protocol violation equivalent to skipping the Victory Gauntlet. **If you find yourself thinking "I don't need the Surfer for this" — that is exactly when you need it most.**
+
+Read the `heralding:` field from `.claude/agents/silver-surfer-herald.md` and announce it before launching.
 
 **How to launch:** Use the Agent tool with these exact parameters:
 - `description`: "Silver Surfer roster scan"

package/.claude/commands/campaign.md

@@ -55,7 +55,9 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 ## Silver Surfer Pre-Scan (ADR-048)
 
-**MANDATORY.** Before deploying any domain agents, launch the Silver Surfer. **Do NOT skip this step.** Before launching, read the `## Cosmic Heraldings` section from `.claude/agents/silver-surfer-herald.md` and announce one at random (never repeat in the same session). Then launch the Surfer.
+**MANDATORY — NO EXCEPTIONS.** Launch the Silver Surfer before deploying ANY other agents. This is not negotiable, not deferrable, and not skippable regardless of how simple the task appears. "The task is simple" is NOT a valid reason to skip — the Surfer catches cross-domain relevance that you cannot predict. "I already know which agents to use" is NOT a valid reason — the Surfer reads agent definitions you haven't loaded. Skipping the Surfer is a protocol violation equivalent to skipping the Victory Gauntlet. **If you find yourself thinking "I don't need the Surfer for this" — that is exactly when you need it most.**
+
+Read the `heralding:` field from `.claude/agents/silver-surfer-herald.md` and announce it before launching.
 
 **How to launch:** Use the Agent tool with these exact parameters:
 - `description`: "Silver Surfer roster scan"

package/.claude/commands/deploy.md

@@ -6,7 +6,9 @@ Read `/docs/methods/DEVOPS_ENGINEER.md` for operating rules (see "Deploy Automat
 
 ## Silver Surfer Pre-Scan (ADR-048)
 
-**MANDATORY.** Before deploying any domain agents, launch the Silver Surfer. **Do NOT skip this step.** Before launching, read the `## Cosmic Heraldings` section from `.claude/agents/silver-surfer-herald.md` and announce one at random (never repeat in the same session). Then launch the Surfer.
+**MANDATORY — NO EXCEPTIONS.** Launch the Silver Surfer before deploying ANY other agents. This is not negotiable, not deferrable, and not skippable regardless of how simple the task appears. "The task is simple" is NOT a valid reason to skip — the Surfer catches cross-domain relevance that you cannot predict. "I already know which agents to use" is NOT a valid reason — the Surfer reads agent definitions you haven't loaded. Skipping the Surfer is a protocol violation equivalent to skipping the Victory Gauntlet. **If you find yourself thinking "I don't need the Surfer for this" — that is exactly when you need it most.**
+
+Read the `heralding:` field from `.claude/agents/silver-surfer-herald.md` and announce it before launching.
 
 **How to launch:** Use the Agent tool with these exact parameters:
 - `description`: "Silver Surfer roster scan"

package/.claude/commands/devops.md

@@ -13,7 +13,9 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 ## Silver Surfer Pre-Scan (ADR-048)
 
-**MANDATORY.** Before deploying any domain agents, launch the Silver Surfer. **Do NOT skip this step.** Before launching, read the `## Cosmic Heraldings` section from `.claude/agents/silver-surfer-herald.md` and announce one at random (never repeat in the same session). Then launch the Surfer.
+**MANDATORY — NO EXCEPTIONS.** Launch the Silver Surfer before deploying ANY other agents. This is not negotiable, not deferrable, and not skippable regardless of how simple the task appears. "The task is simple" is NOT a valid reason to skip — the Surfer catches cross-domain relevance that you cannot predict. "I already know which agents to use" is NOT a valid reason — the Surfer reads agent definitions you haven't loaded. Skipping the Surfer is a protocol violation equivalent to skipping the Victory Gauntlet. **If you find yourself thinking "I don't need the Surfer for this" — that is exactly when you need it most.**
+
+Read the `heralding:` field from `.claude/agents/silver-surfer-herald.md` and announce it before launching.
 
 **How to launch:** Use the Agent tool with these exact parameters:
 - `description`: "Silver Surfer roster scan"

package/.claude/commands/gauntlet.md

@@ -17,7 +17,9 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 ## Silver Surfer Pre-Scan (ADR-048)
 
-**MANDATORY.** Before deploying any domain agents, launch the Silver Surfer. **Do NOT skip this step.** Before launching, read the `## Cosmic Heraldings` section from `.claude/agents/silver-surfer-herald.md` and announce one at random (never repeat in the same session). Then launch the Surfer.
+**MANDATORY — NO EXCEPTIONS.** Launch the Silver Surfer before deploying ANY other agents. This is not negotiable, not deferrable, and not skippable regardless of how simple the task appears. "The task is simple" is NOT a valid reason to skip — the Surfer catches cross-domain relevance that you cannot predict. "I already know which agents to use" is NOT a valid reason — the Surfer reads agent definitions you haven't loaded. Skipping the Surfer is a protocol violation equivalent to skipping the Victory Gauntlet. **If you find yourself thinking "I don't need the Surfer for this" — that is exactly when you need it most.**
+
+Read the `heralding:` field from `.claude/agents/silver-surfer-herald.md` and announce it before launching.
 
 **How to launch:** Use the Agent tool with these exact parameters:
 - `description`: "Silver Surfer roster scan"

package/.claude/commands/qa.md

@@ -12,7 +12,9 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 ## Silver Surfer Pre-Scan (ADR-048)
 
-**MANDATORY.** Before deploying any domain agents, launch the Silver Surfer. **Do NOT skip this step.** Before launching, read the `## Cosmic Heraldings` section from `.claude/agents/silver-surfer-herald.md` and announce one at random (never repeat in the same session). Then launch the Surfer.
+**MANDATORY — NO EXCEPTIONS.** Launch the Silver Surfer before deploying ANY other agents. This is not negotiable, not deferrable, and not skippable regardless of how simple the task appears. "The task is simple" is NOT a valid reason to skip — the Surfer catches cross-domain relevance that you cannot predict. "I already know which agents to use" is NOT a valid reason — the Surfer reads agent definitions you haven't loaded. Skipping the Surfer is a protocol violation equivalent to skipping the Victory Gauntlet. **If you find yourself thinking "I don't need the Surfer for this" — that is exactly when you need it most.**
+
+Read the `heralding:` field from `.claude/agents/silver-surfer-herald.md` and announce it before launching.
 
 **How to launch:** Use the Agent tool with these exact parameters:
 - `description`: "Silver Surfer roster scan"

package/.claude/commands/review.md

@@ -10,7 +10,9 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 ## Silver Surfer Pre-Scan (ADR-048)
 
-**MANDATORY.** Before deploying any domain agents, launch the Silver Surfer. **Do NOT skip this step.** Before launching, read the `## Cosmic Heraldings` section from `.claude/agents/silver-surfer-herald.md` and announce one at random (never repeat in the same session). Then launch the Surfer.
+**MANDATORY — NO EXCEPTIONS.** Launch the Silver Surfer before deploying ANY other agents. This is not negotiable, not deferrable, and not skippable regardless of how simple the task appears. "The task is simple" is NOT a valid reason to skip — the Surfer catches cross-domain relevance that you cannot predict. "I already know which agents to use" is NOT a valid reason — the Surfer reads agent definitions you haven't loaded. Skipping the Surfer is a protocol violation equivalent to skipping the Victory Gauntlet. **If you find yourself thinking "I don't need the Surfer for this" — that is exactly when you need it most.**
+
+Read the `heralding:` field from `.claude/agents/silver-surfer-herald.md` and announce it before launching.
 
 **How to launch:** Use the Agent tool with these exact parameters:
 - `description`: "Silver Surfer roster scan"

package/.claude/commands/security.md

@@ -10,7 +10,9 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 ## Silver Surfer Pre-Scan (ADR-048)
 
-**MANDATORY.** Before deploying any domain agents, launch the Silver Surfer. **Do NOT skip this step.** Before launching, read the `## Cosmic Heraldings` section from `.claude/agents/silver-surfer-herald.md` and announce one at random (never repeat in the same session). Then launch the Surfer.
+**MANDATORY — NO EXCEPTIONS.** Launch the Silver Surfer before deploying ANY other agents. This is not negotiable, not deferrable, and not skippable regardless of how simple the task appears. "The task is simple" is NOT a valid reason to skip — the Surfer catches cross-domain relevance that you cannot predict. "I already know which agents to use" is NOT a valid reason — the Surfer reads agent definitions you haven't loaded. Skipping the Surfer is a protocol violation equivalent to skipping the Victory Gauntlet. **If you find yourself thinking "I don't need the Surfer for this" — that is exactly when you need it most.**
+
+Read the `heralding:` field from `.claude/agents/silver-surfer-herald.md` and announce it before launching.
 
 **How to launch:** Use the Agent tool with these exact parameters:
 - `description`: "Silver Surfer roster scan"

package/.claude/commands/test.md

@@ -15,7 +15,9 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 ## Silver Surfer Pre-Scan (ADR-048)
 
-**MANDATORY.** Before deploying any domain agents, launch the Silver Surfer. **Do NOT skip this step.** Before launching, read the `## Cosmic Heraldings` section from `.claude/agents/silver-surfer-herald.md` and announce one at random (never repeat in the same session). Then launch the Surfer.
+**MANDATORY — NO EXCEPTIONS.** Launch the Silver Surfer before deploying ANY other agents. This is not negotiable, not deferrable, and not skippable regardless of how simple the task appears. "The task is simple" is NOT a valid reason to skip — the Surfer catches cross-domain relevance that you cannot predict. "I already know which agents to use" is NOT a valid reason — the Surfer reads agent definitions you haven't loaded. Skipping the Surfer is a protocol violation equivalent to skipping the Victory Gauntlet. **If you find yourself thinking "I don't need the Surfer for this" — that is exactly when you need it most.**
+
+Read the `heralding:` field from `.claude/agents/silver-surfer-herald.md` and announce it before launching.
 
 **How to launch:** Use the Agent tool with these exact parameters:
 - `description`: "Silver Surfer roster scan"

package/.claude/commands/ux.md

@@ -10,7 +10,9 @@ Opus scans `git diff --stat` and matches changed files against the `description`
 
 ## Silver Surfer Pre-Scan (ADR-048)
 
-**MANDATORY.** Before deploying any domain agents, launch the Silver Surfer. **Do NOT skip this step.** Before launching, read the `## Cosmic Heraldings` section from `.claude/agents/silver-surfer-herald.md` and announce one at random (never repeat in the same session). Then launch the Surfer.
+**MANDATORY — NO EXCEPTIONS.** Launch the Silver Surfer before deploying ANY other agents. This is not negotiable, not deferrable, and not skippable regardless of how simple the task appears. "The task is simple" is NOT a valid reason to skip — the Surfer catches cross-domain relevance that you cannot predict. "I already know which agents to use" is NOT a valid reason — the Surfer reads agent definitions you haven't loaded. Skipping the Surfer is a protocol violation equivalent to skipping the Victory Gauntlet. **If you find yourself thinking "I don't need the Surfer for this" — that is exactly when you need it most.**
+
+Read the `heralding:` field from `.claude/agents/silver-surfer-herald.md` and announce it before launching.
 
 **How to launch:** Use the Agent tool with these exact parameters:
 - `description`: "Silver Surfer roster scan"

package/CHANGELOG.md

@@ -6,6 +6,13 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/), and this
 
 ---
 
+## [23.8.1] - 2026-04-12
+
+### Fixed
+- **Silver Surfer anti-skip enforcement hardened** — "MANDATORY" wasn't strong enough. Commands now say "NO EXCEPTIONS" with pre-emptive rebuttals for every rationalization Claude uses to skip ("task is simple", "I already know which agents"). Equated to Victory Gauntlet violation. Psychological inversion: "If you think you don't need the Surfer — that's exactly when you need it most." Operational learning added to Silver Surfer agent definition with field report evidence.
+
+---
+
 ## [23.8.0] - 2026-04-12
 
 ### The Personality (ADR-049)

package/VERSION.md

@@ -1,6 +1,6 @@
 # Version
 
-**Current:** 23.8.0
+**Current:** 23.8.1
 
 ## Versioning Scheme
 
@@ -14,6 +14,7 @@ This project uses [Semantic Versioning](https://semver.org/):
 
 | Version | Date | Summary |
 |---------|------|---------|
+| 23.8.1 | 2026-04-12 | Silver Surfer anti-skip hardening — NO EXCEPTIONS enforcement + field report learning |
 | 23.8.0 | 2026-04-12 | The Personality — heralding one-liners for all 264 agents. Character-authentic announcements on every agent deployment. ADR-049. |
 | 23.7.3 | 2026-04-12 | Cosmic Heraldings — 14 Silver Surfer one-liners announced at random before each roster scan |
 | 23.7.2 | 2026-04-12 | Silver Surfer explicit Agent tool invocation — guaranteed to work in every environment |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "thevoidforge-methodology",
-  "version": "23.8.0",
+  "version": "23.8.1",
   "description": "VoidForge methodology — agents, commands, methods, patterns.",
   "license": "MIT",
   "files": [