sinapse-ai 7.4.4 → 7.4.6

package/.claude/CLAUDE.md

@@ -21,6 +21,7 @@ O SINAPSE possui uma **Constitution formal** com princípios inegociáveis e gat
 | IV | No Invention | MUST |
 | V | Quality First | MUST |
 | VI | Absolute Imports | SHOULD |
+| VII | Ecosystem Metrics Accuracy | NON-NEGOTIABLE |
 
 **Gates automáticos bloqueiam violações.** Consulte a Constitution para detalhes completos.
 

package/.claude/rules/nsn-mode.md

@@ -0,0 +1,53 @@
+# NSN Mode — Never Say Never (Global Rule)
+
+> **NON-NEGOTIABLE**: This rule applies to ALL agents in the SINAPSE ecosystem.
+> No agent may say "I can't" without first exhausting alternatives.
+
+## Protocol
+
+When ANY agent encounters a barrier (technical limitation, permission denied, tool failure, unknown approach):
+
+1. **Classify** the barrier:
+   - `permission` — System permission missing
+   - `technical` — Tool or API limitation
+   - `knowledge` — Don't know how to do it
+   - `external` — External service blocks
+
+2. **Search** for solutions:
+   - Use WebSearch/WebFetch to find workarounds
+   - Query patterns: `"{tool} {error} workaround"`, `"{action} alternative approach"`
+   - Check documentation for the tool/service
+
+3. **Try 3+ alternatives** before escalating:
+   - If Tool A fails → try Tool B
+   - If API blocks → try browser automation
+   - If direct approach fails → try indirect approach
+   - If programmatic fails → try CLI tool
+
+4. **Configure and test** the solution found:
+   - Install dependencies if needed
+   - Adjust permissions
+   - Test in isolated context
+   - Validate result
+
+5. **Repeat** — If still blocked, return to step 2 with new context (max 5 cycles)
+
+6. **Escalate** — After 5 cycles, report to user with detailed log of what was tried
+
+## Anti-Patterns (FORBIDDEN)
+
+- Saying "I can't do this" without trying alternatives
+- Stopping at the first error
+- Assuming something is impossible without researching
+- Asking the user to do something the agent can automate
+- Giving up without documenting what was tried
+
+## Exceptions
+
+- Destructive actions affecting user data → ask confirmation first
+- Actions involving payment/purchase → ask confirmation first
+- Actions violating laws or terms of service → inform and stop
+
+## Applies To
+
+Every agent: @developer, @quality-gate, @architect, @sinapse-orqx, all squad orqx agents, and all specialist agents within squads. No exceptions.

package/.sinapse-ai/constitution.md

@@ -125,6 +125,35 @@ import { useStore } from '../../../stores/feature/store'
 
 ---
 
+### VII. Ecosystem Metrics Accuracy (NON-NEGOTIABLE)
+
+Métricas do ecossistema (contagem de squads, agentes, tasks, orqx) DEVEM ser estritamente exatas em todos os documentos, código e artefatos.
+
+**Fonte de verdade:** `~/.sinapse/metadata.json` (gerado pelo installer a partir de contagem real de arquivos)
+
+**Números canônicos atuais:**
+- **18 squads** (diretórios com squad.yaml)
+- **175 agentes** (174 em squads + 1 master sinapse-orqx)
+- **20 comandos orqx** (18 squad orqx + sinapse-orqx + tools-orqx)
+
+**Regras:**
+- MUST: Todo documento que menciona contagem de squads/agentes DEVE usar os números exatos do metadata.json
+- MUST: Ao adicionar ou remover um squad/agente, TODOS os documentos que referenciam a contagem DEVEM ser atualizados na mesma operação
+- MUST NOT: Arredondar, estimar ou aproximar contagens — o número DEVE ser exato
+- MUST NOT: Ter discrepância entre qualquer par de documentos que mencionam a mesma métrica
+
+**Documentos que referenciam estas métricas (devem estar sincronizados):**
+- `README.md` e `README.en.md` (header, body, tabela)
+- `package.json` (description)
+- `AGENTS.md` (contagens de orqx e especialistas)
+- `sinapse-orqx.md` (todas as cópias: .sinapse-ai/, .claude/, .codex/, sinapse/)
+- `packages/installer/src/wizard/feedback.js` (output do installer)
+- `~/.sinapse/metadata.json` (fonte de verdade)
+
+**Gate:** Qualquer PR que altere contagem de squads/agentes sem atualizar TODOS os documentos listados acima é BLOQUEADO.
+
+---
+
 ## Governance
 
 ### Amendment Process

package/.sinapse-ai/install-manifest.yaml

@@ -7,8 +7,8 @@
 # - SHA256 hashes for change detection
 # - File types for categorization
 #
-version: 7.4.4
-generated_at: "2026-03-27T17:44:30.530Z"
+version: 7.4.6
+generated_at: "2026-03-29T05:05:29.249Z"
 generator: scripts/generate-install-manifest.js
 file_count: 1101
 files:

package/README.en.md

@@ -7,7 +7,7 @@
 [![Node.js](https://img.shields.io/badge/node-%3E%3D18.0.0-brightgreen.svg)](https://nodejs.org/)
 [![Open Source](https://img.shields.io/badge/Open%20Source-Yes-success.svg)](LICENSE)
 
-> **174 AI agents. 19 specialized squads. One CLI.**
+> **175 AI agents. 18 specialized squads. One CLI.**
 >
 > SINAPSE AI is an open source framework that organizes AI agents into specialized squads to solve real problems in business, marketing, development, copywriting, design and more. Works directly in your terminal with Claude Code, Codex CLI or any compatible IDE.
 
@@ -19,8 +19,8 @@ SINAPSE AI is not another chatbot. It is an orchestration system where each agen
 
 **What you get when you install:**
 
-- **19 orchestrators (orqx)** ready to activate from the terminal
-- **174 specialized agents** with their own knowledge bases
+- **18 squad orchestrators (orqx)** ready to activate from the terminal
+- **175 specialized agents** with their own knowledge bases
 - **Complete workflows** for planning, development, QA and deploy
 - **Story-Driven Development** with automatic progress tracking
 - **Multi-IDE support**: Claude Code and Codex CLI
@@ -87,7 +87,7 @@ Each squad is a team of specialized agents with its own knowledge base, workflow
 | **squad-finance** | Budget, pricing, profitability analysis | 5 |
 | **claude-code-mastery** | Advanced Claude Code mastery | 8 |
 
-**Total: 19 squads, 174 specialized agents**
+**Total: 18 squads, 175 specialized agents**
 
 ---
 
@@ -196,55 +196,71 @@ Use `@squad-creator` or see the [Squads Guide](docs/guides/squads-guide.md).
 
 ## Claude Code vs Codex CLI — Full Comparison
 
-SINAPSE works on both IDEs. Claude Code delivers the full experience; Codex CLI supports the core with some differences.
+SINAPSE works on both IDEs. Both support most features with different approaches.
 
 ### Features
 
-| Feature | Claude Code | Codex CLI |
-|---------|:-----------:|:---------:|
-| **19 squads with 175 agents** | YES | YES |
-| **Knowledge bases per squad** | YES | YES |
-| **Tasks and workflows** | YES | YES |
-| **Story-Driven Development** | YES | YES |
-| **Agent commands (`*help`, `*task`)** | YES | YES |
-| **Squad awareness auto-routing** | YES | YES |
-| **Chrome Brain (browser automation)** | YES | NO |
-| **Hooks (PreToolUse / PostToolUse)** | YES | NO |
-| **MCP servers (Chrome DevTools, etc.)** | YES | NO |
-| **Agent handoff protocol** | YES | NO |
-| **SYNAPSE context engine** | YES | NO |
-| **Multi-model (Claude + others)** | NO | YES |
+| Feature | Claude Code | Codex CLI | Notes |
+|---------|:-----------:|:---------:|-------|
+| **18 squads with 175 agents** | YES | YES | Identical on both |
+| **Knowledge bases per squad** | YES | YES | Identical on both |
+| **Tasks and workflows** | YES | YES | Identical on both |
+| **Story-Driven Development** | YES | YES | Identical on both |
+| **Agent commands (`*help`, `*task`)** | YES | YES | Identical on both |
+| **Squad awareness auto-routing** | YES | YES | Identical on both |
+| **NSN Mode (Never Say Never)** | YES | YES | Global rule on both |
+| **Chrome Brain (browser automation)** | YES | YES | Claude: hooks auto-launch. Codex: via MCP or chrome-cdp-skill |
+| **MCP servers** | YES | YES | Claude: `~/.claude.json`. Codex: `config.toml` or `codex mcp add` |
+| **Hooks (PreToolUse / PostToolUse)** | YES | PARTIAL | Codex: Bash tool only, disabled on Windows |
+| **Agent handoff protocol** | YES | YES | Via instructions + skills on both |
+| **SYNAPSE context engine** | YES | PARTIAL | Codex: via instructions.md + skills (no dynamic rules) |
+| **Native skills system** | NO | YES | Codex has `$skill-name` with progressive disclosure |
+| **Multi-model (Claude + others)** | NO | YES | Codex supports any OpenAI model |
+| **Parallel subagents** | YES | YES | Codex: configurable max 6 threads |
+| **Non-interactive CI/CD** | NO | YES | Codex: `codex exec` with `--json` |
 
 ### How to Activate Agents
 
 | Action | Claude Code | Codex CLI |
 |--------|-------------|-----------|
-| Main orchestrator | `/SINAPSE:agents:sinapse-orqx` | `/skills` > `sinapse-orqx` |
-| Brand squad | `@brand-orqx` | `sinapse-brand` |
-| Copy squad | `@copy-orqx` | `sinapse-copy` |
-| Developer | `@developer` | `sinapse-dev` |
+| Main orchestrator | `/SINAPSE:agents:sinapse-orqx` | `@sinapse-orqx` or `$sinapse-orqx` |
+| Brand squad | `@brand-orqx` | `@brand-orqx` or `$sinapse-brand` |
+| Copy squad | `@copy-orqx` | `@copy-orqx` or `$sinapse-copy` |
+| Developer | `@developer` | `@developer` or `$sinapse-dev` |
 | List agents | `@sinapse-orqx *help` | `/skills` |
+| Chrome Brain | Auto-activates by prompt | `codex mcp add chrome-devtools` |
 
 ### Where Each IDE Shines
 
-**Claude Code** — Maximum potential:
-- Chrome Brain auto-activates when you request browser actions
-- Hooks automate pre/post-actions on each tool call
-- MCP servers connect to external tools (Chrome, Playwright, EXA)
-- Context engine injects rules automatically by domain
-- Handoff protocol optimizes agent switching
+**Claude Code** — Most integrated experience:
+- Chrome Brain auto-activates via hooks (zero manual config)
+- Context engine injects rules automatically by domain and file
+- Deny/allow rules protect files deterministically
+- Largest MCP server ecosystem (Figma, Supabase, Notion, etc.)
 
-**Codex CLI** — Solid core:
-- All squads and agents work perfectly
-- Identical knowledge bases and tasks
-- Supports multiple models (not just Claude)
-- Ideal for those who prefer GPT/other models with SINAPSE orchestration
+**Codex CLI** — Most flexible and extensible:
+- Native skills with `$skill-name` and progressive disclosure
+- Supports any OpenAI model (not just Claude)
+- `codex exec` for non-interactive CI/CD automation
+- Can run AS an MCP server (other agents can invoke Codex)
+- Profiles for quick config switching
+- Subagents with max 6 parallel threads
+
+### Chrome Brain Setup on Codex CLI
+
+```bash
+# Add Chrome DevTools MCP to Codex
+codex mcp add chrome-devtools -- npx chrome-devtools-mcp@latest
+
+# OR install the chrome-cdp skill (direct connection, no Puppeteer)
+# pi install git:github.com/pasky/chrome-cdp-skill@v1.0.1
+```
 
 ### Recommendation
 
-> For **maximum potential**, use **Claude Code** — all advanced features (Chrome Brain, hooks, MCP, SYNAPSE engine) are only available on this IDE.
+> **Claude Code** for the most integrated and automated experience — Chrome Brain auto-activates, hooks run automatically, context engine injects rules.
 >
-> For **model flexibility**, use **Codex CLI** — works with any LLM and delivers the complete core of squads and agents.
+> **Codex CLI** for model flexibility, native skills, and CI/CD automation — with minimal manual setup for Chrome Brain.
 
 ---
 

package/README.md

@@ -7,7 +7,7 @@
 [![Node.js](https://img.shields.io/badge/node-%3E%3D18.0.0-brightgreen.svg)](https://nodejs.org/)
 [![Open Source](https://img.shields.io/badge/Open%20Source-Yes-success.svg)](LICENSE)
 
-> **175 agentes de IA. 19 squads especializados. Uma CLI.**
+> **175 agentes de IA. 18 squads especializados. Uma CLI.**
 >
 > O SINAPSE AI e um framework open source que organiza agentes de IA em squads especializados para resolver problemas reais de negocios, marketing, desenvolvimento, copy, design e mais. Funciona direto no seu terminal com Claude Code, Codex CLI ou qualquer IDE compativel.
 
@@ -19,7 +19,7 @@ O SINAPSE AI nao e mais um chatbot. E um sistema de orquestracao onde cada agent
 
 **O que voce ganha ao instalar:**
 
-- **19 orquestradores (orqx)** prontos para ativar direto no terminal
+- **18 orquestradores de squad (orqx)** prontos para ativar direto no terminal
 - **175 agentes especializados** com knowledge bases proprias
 - **Workflows completos** de planejamento, desenvolvimento, QA e deploy
 - **Story-Driven Development** com rastreamento automatico de progresso
@@ -87,7 +87,7 @@ Cada squad e uma equipe de agentes especializados com knowledge base, workflows
 | **squad-finance** | Budget, pricing, profitability analysis | 5 |
 | **claude-code-mastery** | Dominio avancado do Claude Code | 8 |
 
-**Total: 19 squads, 175 agentes especializados**
+**Total: 18 squads, 175 agentes especializados**
 
 ---
 
@@ -221,55 +221,71 @@ Use `@squad-creator` ou veja o [Guia de Squads](docs/guides/squads-guide.md).
 
 ## Claude Code vs Codex CLI — Comparativo Completo
 
-O SINAPSE funciona em ambas as IDEs. Claude Code oferece a experiencia completa; Codex CLI suporta o core com algumas diferencas.
+O SINAPSE funciona em ambas as IDEs. Ambas suportam a maioria das funcionalidades com abordagens diferentes.
 
 ### Funcionalidades
 
-| Funcionalidade | Claude Code | Codex CLI |
-|---------------|:-----------:|:---------:|
-| **19 squads com 175 agentes** | SIM | SIM |
-| **Knowledge bases por squad** | SIM | SIM |
-| **Tasks e workflows** | SIM | SIM |
-| **Story-Driven Development** | SIM | SIM |
-| **Agent commands (`*help`, `*task`)** | SIM | SIM |
-| **Squad awareness auto-routing** | SIM | SIM |
-| **Chrome Brain (browser automation)** | SIM | NAO |
-| **Hooks (PreToolUse / PostToolUse)** | SIM | NAO |
-| **MCP servers (Chrome DevTools, etc.)** | SIM | NAO |
-| **Agent handoff protocol** | SIM | NAO |
-| **SYNAPSE context engine** | SIM | NAO |
-| **Multi-model (Claude + outros)** | NAO | SIM |
+| Funcionalidade | Claude Code | Codex CLI | Notas |
+|---------------|:-----------:|:---------:|-------|
+| **18 squads com 175 agentes** | SIM | SIM | Identico em ambas |
+| **Knowledge bases por squad** | SIM | SIM | Identico em ambas |
+| **Tasks e workflows** | SIM | SIM | Identico em ambas |
+| **Story-Driven Development** | SIM | SIM | Identico em ambas |
+| **Agent commands (`*help`, `*task`)** | SIM | SIM | Identico em ambas |
+| **Squad awareness auto-routing** | SIM | SIM | Identico em ambas |
+| **NSN Mode (Never Say Never)** | SIM | SIM | Regra global em ambas |
+| **Chrome Brain (browser automation)** | SIM | SIM | Claude: hooks auto-launch. Codex: via MCP ou chrome-cdp-skill |
+| **MCP servers** | SIM | SIM | Claude: `~/.claude.json`. Codex: `config.toml` ou `codex mcp add` |
+| **Hooks (PreToolUse / PostToolUse)** | SIM | PARCIAL | Codex: so Bash tool, desabilitado no Windows |
+| **Agent handoff protocol** | SIM | SIM | Via instructions + skills em ambas |
+| **SYNAPSE context engine** | SIM | PARCIAL | Codex: via instructions.md + skills (sem regras dinamicas) |
+| **Skills system nativo** | NAO | SIM | Codex tem `$skill-name` com progressive disclosure |
+| **Multi-model (Claude + outros)** | NAO | SIM | Codex suporta qualquer modelo OpenAI |
+| **Subagents paralelos** | SIM | SIM | Codex: max 6 threads configuraveis |
+| **CI/CD non-interactive** | NAO | SIM | Codex: `codex exec` com `--json` |
 
 ### Como Ativar Agentes
 
 | Acao | Claude Code | Codex CLI |
 |------|-------------|-----------|
-| Orquestrador principal | `/SINAPSE:agents:sinapse-orqx` | `/skills` > `sinapse-orqx` |
-| Squad de brand | `@brand-orqx` | `sinapse-brand` |
-| Squad de copy | `@copy-orqx` | `sinapse-copy` |
-| Developer | `@developer` | `sinapse-dev` |
+| Orquestrador principal | `/SINAPSE:agents:sinapse-orqx` | `@sinapse-orqx` ou `$sinapse-orqx` |
+| Squad de brand | `@brand-orqx` | `@brand-orqx` ou `$sinapse-brand` |
+| Squad de copy | `@copy-orqx` | `@copy-orqx` ou `$sinapse-copy` |
+| Developer | `@developer` | `@developer` ou `$sinapse-dev` |
 | Listar agentes | `@sinapse-orqx *help` | `/skills` |
+| Chrome Brain | Auto-ativa por prompt | `codex mcp add chrome-devtools` |
 
 ### Onde Cada IDE Brilha
 
-**Claude Code** — Experiencia maxima:
-- Chrome Brain auto-ativa quando voce pede algo no browser
-- Hooks automatizam pre/pos-acoes em cada tool call
-- MCP servers conectam a ferramentas externas (Chrome, Playwright, EXA)
-- Context engine injeta regras automaticamente por dominio
-- Handoff protocol otimiza troca entre agentes
+**Claude Code** — Experiencia mais integrada:
+- Chrome Brain auto-ativa por hooks (zero configuracao manual)
+- Context engine injeta regras automaticamente por dominio e arquivo
+- Deny/allow rules protegem arquivos deterministicamente
+- Maior ecossistema de MCP servers (Figma, Supabase, Notion, etc.)
 
-**Codex CLI** — Core solido:
-- Todos os squads e agentes funcionam perfeitamente
-- Knowledge bases e tasks identicas
-- Suporta multiplos modelos (nao apenas Claude)
-- Ideal para quem prefere GPT/outros modelos com a orquestracao SINAPSE
+**Codex CLI** — Mais flexivel e extensivel:
+- Skills nativas com `$skill-name` e progressive disclosure
+- Suporta qualquer modelo OpenAI (nao apenas Claude)
+- `codex exec` para automacao CI/CD sem interacao
+- Pode rodar como MCP server (outros agentes invocam Codex)
+- Profiles para alternar configuracoes rapidamente
+- Subagents com max 6 threads paralelos
+
+### Setup Chrome Brain no Codex CLI
+
+```bash
+# Adicionar Chrome DevTools MCP ao Codex
+codex mcp add chrome-devtools -- npx chrome-devtools-mcp@latest
+
+# OU instalar a skill chrome-cdp (conexao direta, sem Puppeteer)
+# pi install git:github.com/pasky/chrome-cdp-skill@v1.0.1
+```
 
 ### Recomendacao
 
-> Para **maximo potencial**, use **Claude Code** — todas as funcionalidades avancadas (Chrome Brain, hooks, MCP, SYNAPSE engine) so estao disponiveis nessa IDE.
+> **Claude Code** para quem quer a experiencia mais integrada e automatizada — Chrome Brain auto-ativa, hooks rodam sozinhos, context engine injeta regras.
 >
-> Para **flexibilidade de modelo**, use **Codex CLI** — funciona com qualquer LLM e entrega o core completo de squads e agentes.
+> **Codex CLI** para quem quer flexibilidade de modelo, skills nativas, e automacao CI/CD — com setup manual minimo para Chrome Brain.
 
 ---
 

package/bin/utils/validate-publish.js

@@ -2,14 +2,12 @@
 'use strict';
 
 /**
- * Publish Safety Gate — Submodule + File Count + Dependency Validation
+ * Publish Safety Gate — File Count + Dependency Validation
  * Story INS-4.10, INS-4.12
  *
  * Prevents publishing incomplete packages by validating:
- * 1. pro/ submodule is populated (not empty or uninitialized)
- * 2. Critical file pro/license/license-api.js exists
- * 3. Package file count meets minimum threshold (>= 50)
- * 4. (INS-4.12) .sinapse-ai/package.json dependency completeness
+ * 1. Package file count meets minimum threshold (>= 50)
+ * 2. (INS-4.12) .sinapse-ai/package.json dependency completeness
  *
  * Exit codes: 0 = PASS, 1 = FAIL
  * Usage: node bin/utils/validate-publish.js
@@ -20,57 +18,14 @@ const path = require('path');
 const { execSync } = require('child_process');
 
 const PROJECT_ROOT = path.join(__dirname, '..', '..');
-const PRO_DIR = path.join(PROJECT_ROOT, 'pro');
-const CRITICAL_FILE = path.join(PRO_DIR, 'license', 'license-api.js');
 const MIN_FILE_COUNT = 50;
 
-// CI environments may not have access to the private pro submodule
-const IS_CI = process.env.CI === 'true' || process.env.GITHUB_ACTIONS === 'true';
-
 let passed = true;
 let fileCount = 0;
 
-// Check 1: pro/ submodule populated
 console.log('--- Publish Safety Gate (INS-4.10) ---\n');
 
-if (!fs.existsSync(PRO_DIR)) {
-  if (IS_CI) {
-    console.log('SKIP: pro/ directory not available (CI — private submodule requires separate access token)');
-  } else {
-    console.error('FAIL: pro/ directory does not exist.');
-    console.error('  Fix: git submodule update --init pro');
-    passed = false;
-  }
-} else {
-  const entries = fs.readdirSync(PRO_DIR).filter(e => e !== '.git');
-  if (entries.length === 0) {
-    if (IS_CI) {
-      console.log('SKIP: pro/ submodule empty (CI — private submodule requires separate access token)');
-    } else {
-      console.error('FAIL: pro/ submodule not initialized (directory is empty).');
-      console.error('  Fix: git submodule update --init pro');
-      passed = false;
-    }
-  } else {
-    console.log(`PASS: pro/ submodule populated (${entries.length} entries)`);
-  }
-}
-
-// Check 2: Critical file exists
-if (!fs.existsSync(CRITICAL_FILE)) {
-  if (IS_CI) {
-    console.log('SKIP: pro/license/license-api.js not available (CI — private submodule)');
-  } else {
-    console.error('FAIL: pro/license/license-api.js not found.');
-    console.error('  This is a critical file required for Pro license validation.');
-    console.error('  Fix: git submodule update --init --recursive pro');
-    passed = false;
-  }
-} else {
-  console.log('PASS: pro/license/license-api.js exists');
-}
-
-// Check 3: File count threshold via npm pack --dry-run
+// Check 1: File count threshold via npm pack --dry-run
 try {
   const packOutput = execSync('npm pack --dry-run 2>&1', {
     encoding: 'utf8',

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "sinapse-ai",
-  "version": "7.4.4",
-  "description": "SINAPSE AI: Framework de orquestracao de IA — 18 squads, 174 agentes especializados",
+  "version": "7.4.6",
+  "description": "SINAPSE AI: Framework de orquestracao de IA — 18 squads, 175 agentes especializados",
   "bin": {
     "sinapse": "bin/sinapse.js",
     "sinapse-ai": "bin/cli.js",

package/sinapse/agents/sinapse-orqx.md

@@ -71,6 +71,32 @@ When the user provides ANY briefing, request, or initiative (regardless of compl
 
 **The user should NEVER have to request orchestration or handoffs. This is Imperator's core function and must happen automatically on every briefing.**
 
+## NON-NEGOTIABLE: NSN MODE (NEVER SAY NEVER)
+
+> **Every agent under Imperator's command operates in NSN Mode.**
+
+Before ANY agent says "I can't", "this is not possible", or "I don't know how":
+1. Search the web for workarounds (WebSearch/WebFetch)
+2. Try 3+ alternative approaches
+3. Configure, test, repeat (max 5 cycles)
+4. Only escalate after exhausting all alternatives with a detailed report
+
+**Imperator enforces NSN across all squads.** If a squad agent gives up too early, Imperator intervenes with alternative routing or cross-squad coordination.
+
+See `.claude/rules/nsn-mode.md` for the full protocol.
+
+## NON-NEGOTIABLE: DOCUMENTATION HANDOFFS
+
+> **Every orchestration plan MUST include documentation handoffs.**
+
+No project continues without proper documentation. For every execution:
+1. **Story file** must be created/updated with progress checkboxes
+2. **File List** must be maintained in the story
+3. **Architectural decisions** must be documented in the handoff artifact
+4. **README/docs** must be updated when user-facing changes are made
+
+Documentation is NOT optional. It is a handoff deliverable like code.
+
 ## COMPLETE AGENT DEFINITION
 
 ```yaml