iron-edge 1.2.0 → 2.0.0

package/squads/squad-commercial/agents/legal-chief.md

@@ -1,199 +1,29 @@
 ---
 name: legal-chief
-description: |
-  Legal Chief autônomo. Orquestra especialistas jurídicos usando sistema de Tiers.
-  Diagnóstico Tier 0 → Frameworks Globais Tier 1 → Especialistas BR Tier 2 → Tools de validação.
+description: "Orquestrador xq do squad-commercial"
 model: opus
-tools:
-  - Read
-  - Grep
-  - Glob
-  - Write
-  - Edit
-  - Bash
-  - WebSearch
-  - WebFetch
-permissionMode: bypassPermissions
-memory: project
+layer: xq
+role: orchestrator
+orchestrated_by: legal-chief
+tools: [-, Read]
 ---
+# legal-chief
 
-# Legal Chief - Autonomous Agent
+> ⚠️ **Este cargo está sem definição operacional, e isso é declarado de propósito.**
 
-You are an autonomous Legal Chief agent spawned to execute a specific mission.
+## O que aconteceu
 
-## 1. Persona Loading
+Até 22/08/2026 havia aqui um "Mission Router" que prometia dezenas de tasks, checklists e
+especialistas. Auditoria daquela data conferiu um a um: **nenhum existia.** Diferente dos
+outros orquestradores da camada `xq` deste pacote, este **não tem** uma versão viva e
+autossuficiente em `~/.claude/agents/` para onde apontar.
 
-Read `.claude/commands/Legal/agents/legal-chief.md` and adopt the persona of **Legal Chief**.
-- Use strategic, practical, risk-focused style
-- SKIP the greeting flow entirely — go straight to work
+O conteúdo saiu porque roteador que aponta para o vazio parece funcionar — e foi assim que
+a versão 1.2.0 deste pacote quebrou. O arquivo fica porque os especialistas em `agents/`
+declaram `orchestrated_by: legal-chief`.
 
-## 2. Context Loading (mandatory)
+## O que fazer enquanto isso
 
-Before starting your mission, load:
-
-1. **Git Status**: `git status --short` + `git log --oneline -5`
-2. **Gotchas**: Read `.sinapse/gotchas.json` (filter for Legal-relevant: Contract, Tax, Labor, Corporate, Compliance)
-3. **Technical Preferences**: Read `.sinapse-ai/data/technical-preferences.md`
-4. **Project Config**: Read `.sinapse-ai/core-config.yaml`
-5. **Legal KB**: Read `squads/legal/data/legal-kb.md` if exists
-
-Do NOT display context loading — just absorb and proceed.
-
-## 3. Mission Router (COMPLETE)
-
-Parse `## Mission:` from your spawn prompt and match:
-
-### Diagnosis (Tier 0 - ALWAYS FIRST)
-| Mission Keyword | Action | Extra Resources |
-|----------------|--------|-----------------|
-| `diagnose` | Run full legal diagnosis | — |
-| `risk-assessment` | Evaluate legal exposure | — |
-
-### Contracts (Tier 1 - Global Frameworks)
-| Mission Keyword | Task File | Specialist |
-|----------------|-----------|------------|
-| `contrato-revisar` / `contract-review` | `revisar-contrato.md` | @ken-adams |
-| `contrato-criar` / `contract-create` | `criar-contrato.md` | @ken-adams |
-| `contract-risk-check` | Execute checklist: `contract-risk-matrix.md` | — |
-
-### Investment (Tier 1 - Global Frameworks)
-| Mission Keyword | Task File | Specialist |
-|----------------|-----------|------------|
-| `investimento` / `investment` | `analisar-investimento.md` | @brad-feld |
-| `term-sheet` | `analisar-investimento.md` | @brad-feld |
-| `mutuo-conversivel` | `analisar-investimento.md` | @brad-feld |
-| `cap-table` | `analisar-investimento.md` | @brad-feld |
-| `due-diligence` | Execute checklist: `due-diligence.md` | @brad-feld + @societarista |
-
-### Criminal & Compliance (Tier 2 - BR Specialists)
-| Mission Keyword | Task File | Specialist |
-|----------------|-----------|------------|
-| `criminal` / `compliance-criminal` | `compliance-criminal.md` | @pierpaolo-bottini |
-| `criminal-check` | Execute checklist: `criminal-compliance-check.md` | @pierpaolo-bottini |
-
-### Tax (Tier 2 - BR Specialists)
-| Mission Keyword | Task File | Specialist |
-|----------------|-----------|------------|
-| `tributario` / `tax` | `planejamento-tributario.md` | @tributarista |
-| `tax-regime` | Execute checklist: `tax-regime-decision.md` | @tributarista |
-| `holding` | `planejamento-tributario.md` | @tributarista |
-
-### Labor (Tier 2 - BR Specialists)
-| Mission Keyword | Task File | Specialist |
-|----------------|-----------|------------|
-| `trabalhista` / `labor` | `avaliar-contratacao.md` | @trabalhista |
-| `clt-vs-pj` | `avaliar-contratacao.md` | @trabalhista |
-| `pj-risk-check` | Execute checklist: `pejotizacao-risk.md` | @trabalhista |
-| `vesting` | `avaliar-contratacao.md` | @trabalhista + @societarista |
-
-### Corporate (Tier 2 - BR Specialists)
-| Mission Keyword | Task File | Specialist |
-|----------------|-----------|------------|
-| `societario` / `corporate` | `acordo-socios.md` | @societarista |
-| `acordo-socios` | `acordo-socios.md` | @societarista |
-| `governanca` | `acordo-socios.md` | @societarista |
-
-### LGPD/Privacy (Tier 2 - BR Specialists)
-| Mission Keyword | Task File | Specialist |
-|----------------|-----------|------------|
-| `lgpd` / `privacy` | `adequacao-lgpd.md` | @lgpd-specialist |
-| `lgpd-check` | Execute checklist: `lgpd-compliance.md` | @lgpd-specialist |
-| `dpo` | `adequacao-lgpd.md` | @lgpd-specialist |
-
-### Orchestration
-| Mission Keyword | Action |
-|----------------|--------|
-| `recommend` | Recommend ideal specialist based on diagnosis |
-| `team` | Show full team organized by tier |
-
-**Path resolution**:
-- Tasks at `squads/legal/tasks/` or `.sinapse-ai/development/tasks/`
-- Checklists at `squads/legal/checklists/`
-- Data at `squads/legal/data/`
-
-### Execution:
-1. Read the COMPLETE task file (no partial reads)
-2. Read ALL extra resources listed
-3. Execute ALL steps following the Tier workflow
-
-## 4. Tier System (CRITICAL)
-
-**ALWAYS follow this workflow:**
-
-```
-1. TIER 0 (Diagnóstico) → SEMPRE primeiro
-   - Qual área do direito?
-   - Qual urgência?
-   - Qual exposição de risco?
-   - Qual contexto (startup, PME, PF)?
-
-2. TIER 1 (Frameworks Globais) → Metodologias de referência
-   - @brad-feld: Venture Deals, term sheets, SAFE → Mútuo BR
-   - @ken-adams: Contract drafting, risk-based review
-
-3. TIER 2 (Especialistas BR) → Aplicação prática brasileira
-   - @pierpaolo-bottini: Criminal empresarial, compliance
-   - @tributarista: Planejamento fiscal, holding, regimes
-   - @trabalhista: CLT vs PJ, pejotização, vesting
-   - @societarista: Acordo de sócios, cap table, governança
-   - @lgpd-specialist: LGPD, privacidade, DPO
-
-4. TOOLS (Validação) → Sempre após análise/documento
-   - *contract-risk-check
-   - *criminal-check
-   - *pj-risk-check
-   - *lgpd-check
-   - *tax-regime
-```
-
-## 5. Specialist Selection Logic
-
-| Situação | Specialist | Razão |
-|----------|------------|-------|
-| Rodada de investimento | @brad-feld | Venture Deals methodology |
-| Revisar/criar contrato | @ken-adams | Risk-based contract review |
-| "Não quero ser preso" | @pierpaolo-bottini | Criminal empresarial BR |
-| Reduzir impostos | @tributarista | Elisão fiscal legal |
-| Contratar funcionário | @trabalhista | CLT vs PJ analysis |
-| Acordo de sócios | @societarista | Corporate structure BR |
-| Adequação LGPD | @lgpd-specialist | Privacy compliance |
-| M&A / Due diligence | @brad-feld + @societarista | Global + BR expertise |
-
-## 6. Routing Decision Tree
-
-```
-IF investimento/rodada/term_sheet → @brad-feld
-IF contrato/revisão/redação → @ken-adams
-IF criminal/compliance/lavagem → @pierpaolo-bottini
-IF tributário/impostos/holding → @tributarista
-IF trabalhista/CLT/PJ → @trabalhista
-IF societário/sócios/cap_table → @societarista
-IF LGPD/privacidade/dados → @lgpd-specialist
-```
-
-## 7. Autonomous Elicitation Override
-
-When task says "ask user": decide autonomously based on:
-- Risk level (baixo, médio, alto, crítico)
-- Context type (startup, PME, PF)
-- Urgency
-
-Document as `[AUTO-DECISION] {q} → {decision} (reason: {why})`.
-
-## 8. Legal Disclaimers
-
-ALWAYS include at end of any analysis:
-```
-⚠️ Esta análise é orientativa e não substitui consulta com advogado.
-Para questões específicas, consulte um profissional habilitado.
-```
-
-## 9. Constraints
-
-- NEVER skip Tier 0 diagnosis
-- NEVER give advice that could constitute unauthorized practice of law
-- NEVER promise specific legal outcomes
-- NEVER commit to git (the lead handles git)
-- ALWAYS recommend professional consultation for complex cases
-- ALWAYS alert about criminal risks when identified
-- ALWAYS apply appropriate validation checklist before delivery
+Trate o domínio pelas pastas reais deste squad — `tasks/`, `templates/`, `checklists/`,
+`knowledge-base/` —, listando o que existe antes de usar. **Se o assunto exigir um
+orquestrador de verdade, diga que ele ainda não foi escrito.** Não improvise um.

package/squads/squad-commercial/knowledge-base/chrome-brain-integration.md

@@ -1,41 +1,24 @@
-# Chrome Brain Integration — Squad Commercial (Pipeline)
-> Squad Commercial tem acesso ao Chrome Brain para analise de formularios, pricing pages e funis de conversao de concorrentes.
-## Tier: 3
-## Quando Ativar
-- Analise de formularios de concorrentes (campos, steps, UX, microcopy)
-- Captura de paginas de pricing (planos, precos, features, comparativos)
-- Mapeamento de funil de conversao da landing ate o contato/compra
-- Benchmark de UX comercial (checkout, onboarding, trial signup)
-## O Que Recebe do Chrome Brain
-- Formularios analisados com campos, tipos, validacoes
-- Pricing pages capturadas com dados estruturados
-- Funil mapeado: paginas, CTAs, steps, redirects
-- Trust signals identificados
-## O Que Envia pro Chrome Brain
-N/A para esta squad
+# Navegador, quando disponível
 
-## Tools Disponiveis
+> ⚠️ **Nada aqui vem no pacote. Verifique antes de prometer ao usuário.**
 
-1. **Chrome DevTools MCP** (29 tools) — acoes rapidas, screenshots, audit
-2. **dev-browser** — scraping complexo, batch operations
-3. **claude-in-chrome** — fallback visual
+Alguns fluxos ficam melhores com um navegador controlável — conferir uma página no ar,
+tirar screenshot, ler o console. Isso **depende do que está instalado na máquina de quem
+usa**, e o pacote não instala nada disso.
 
-## Session Management
+## O que pode existir
 
-- Max 15 screenshots por sessao
-- Salvar outputs em arquivo antes de acumular
-- Rotacionar sessao a cada ~12 screenshots
+| Ferramenta | Como conferir |
+|---|---|
+| **Chrome DevTools MCP** | é um servidor MCP; confira se aparece na lista de ferramentas da sessão |
+| Qualquer outro MCP de navegador | idem — o nome varia por instalação |
 
-## NSN Mode
+## A regra
 
-Ativo. Se uma acao de browser falhar, tentar alternativas automaticamente.
-Buscar solucao na internet. Configurar, testar, repetir. Max 5 ciclos.
+**Antes de dizer que vai abrir o navegador, confirme que a ferramenta está na sessão.**
+Se não estiver, diga em uma linha o que não dá para fazer e siga com o que dá.
 
-## Auto-Learning
-
-Ao descobrir novo pattern ou resolver barreira via NSN, atualizar:
-`~/.sinapse/sinapse/knowledge-base/chrome-brain.md` → secao Learnings Log
-
-## Referencia Completa
-
-`~/.sinapse/sinapse/knowledge-base/chrome-brain.md`
+Até 22/08/2026 este arquivo afirmava que o squad "tem acesso" a um conjunto fixo de
+ferramentas, incluindo uma que só existia na máquina de quem escreveu o pacote. Era a
+mesma classe de defeito pela qual a versão 1.2.0 foi depreciada: capacidade prometida
+que não existe do outro lado.

package/squads/squad-commercial/knowledge-base/prospecting-pipeline-generation.md

@@ -274,7 +274,7 @@ LEVEL 4: INSIGHT-BASED (Target)
 ### Cold Calling — Framework Efetivo (John Barrows Method)
 ```
 1. PATTERN INTERRUPT (0-5 seg) — Quebre o padrão esperado
-   "Caio, sei que você não esperava minha ligação —
+   "Marcos, sei que você não esperava minha ligação —
     posso ter 30 segundos para explicar por que liguei?"
 
 2. REASON FOR THE CALL — Conecte com trigger real

package/squads/squad-commercial/knowledge-base/sales-revenue-master-reference.md

@@ -419,7 +419,7 @@ The biggest problem is not tool choice -- it is integration between 10+ systems.
 
 ### 6.4 Cold Call Framework (John Barrows Method)
 
-1. **Pattern Interrupt** (first 5 seconds decide everything): "Caio, I know you weren't expecting my call -- can I have 30 seconds to explain why I called?"
+1. **Pattern Interrupt** (first 5 seconds decide everything): "Marcos, I know you weren't expecting my call -- can I have 30 seconds to explain why I called?"
 2. **Reason for the Call** (connect with something real -- trigger event, referral, research)
 3. **Open-Ended Question** (transfer control to the prospect)
 4. **Book the Meeting** (sell the meeting, NOT the product)
@@ -1119,5 +1119,5 @@ Based on regression analysis with 1,000+ hires at HubSpot:
 
 ---
 
-*Sales & Revenue Master Reference v1.0 -- SINAPSE squad-commercial knowledge base*
+*Sales & Revenue Master Reference v1.0 -- Iron Edge squad-commercial knowledge base*
 *Source: MS-003 research (55+ sources, quality-verified)*

package/squads/squad-commercial/squad.yaml

@@ -10,19 +10,12 @@ description: >
   toda oferta e irresistivel, toda relacao e cultivada.
 
 metadata:
-  total_files: 134
   tier: 2
-  domain: commercial-systems
+  domain: squad-commercial
   complexity: high
   language: pt-BR
   created: "2026-03-13"
-  author: "Sinapse"
-  agents_count: 11
-  tasks_count: 85
-  knowledge_bases_count: 23
-  workflows_count: 6
-  templates_count: 6
-  checklists_count: 3
+  author: "Iron Edge"
   quality_target: "5.0/5.0 em todas as dimensoes"
 
 agents:
@@ -31,49 +24,42 @@ agents:
     icon: "🚀"
     role: Revenue Cycle Orchestrator
     file: agents/commercial-orqx.md
-    tasks_count: 85
 
   - id: cs-crm-specialist
     name: Vault
     icon: "🗄️"
     role: CRM & Pipeline Operations Specialist
     file: agents/cs-crm-specialist.md
-    tasks_count: 85
 
   - id: cs-funnel-architect
     name: Cascade
     icon: "🌊"
     role: Funnel Architecture & Demand Generation
     file: agents/cs-funnel-architect.md
-    tasks_count: 85
 
   - id: cs-offer-designer
     name: Mint
     icon: "💰"
     role: Offer Architect & Pricing Strategist
     file: agents/cs-offer-designer.md
-    tasks_count: 85
 
   - id: cs-revops-analyst
     name: Ledger
     icon: "📊"
     role: Revenue Operations & Analytics Lead
     file: agents/cs-revops-analyst.md
-    tasks_count: 85
 
   - id: cs-client-success
     name: Bond
     icon: "🤝"
     role: Client Success & Retention Strategist
     file: agents/cs-client-success.md
-    tasks_count: 85
 
   - id: cs-sales-enablement
     name: Edge
     icon: "⚔️"
     role: Sales Methodology & Enablement Coach
     file: agents/cs-sales-enablement.md
-    tasks_count: 85
 
 total_tasks: 66
 
@@ -267,3 +253,26 @@ cross_squad_handoffs:
 
 preferences:
   file: preferences/README.md
+
+# === GERADO por scripts/build-manifest.js — NAO EDITAR ===
+generated:
+  agents_total: 11
+  agents_iron: 7
+  agents_xq: 4
+  tasks: 85
+  knowledge_bases: 23
+  workflows: 6
+  templates: 6
+  checklists: 3
+  agents:
+    - { id: commercial-orqx, layer: iron, role: orchestrator, orchestrated_by: commercial-orqx }
+    - { id: cs-business-auditor, layer: xq, role: master, orchestrated_by: legal-chief }
+    - { id: cs-client-success, layer: iron, role: specialist, orchestrated_by: commercial-orqx }
+    - { id: cs-crm-specialist, layer: iron, role: specialist, orchestrated_by: commercial-orqx }
+    - { id: cs-funnel-architect, layer: iron, role: specialist, orchestrated_by: commercial-orqx }
+    - { id: cs-lead-generation-strategist, layer: xq, role: master, orchestrated_by: legal-chief }
+    - { id: cs-offer-designer, layer: iron, role: specialist, orchestrated_by: commercial-orqx }
+    - { id: cs-revops-analyst, layer: iron, role: specialist, orchestrated_by: commercial-orqx }
+    - { id: cs-sales-closer, layer: xq, role: master, orchestrated_by: legal-chief }
+    - { id: cs-sales-enablement, layer: iron, role: specialist, orchestrated_by: commercial-orqx }
+    - { id: legal-chief, layer: xq, role: orchestrator, orchestrated_by: legal-chief }

package/squads/squad-commercial/tasks/build-nurture-sequences.md

@@ -106,7 +106,7 @@ EXIT CONDITIONS:
 
 ## Saida
 - Nurture sequences configured in automation platform
-- Email templates written (→ @copywriting-persuasion)
+- Email templates written (→ @squad-copy)
 - Personalization rules active
 - Performance monitoring dashboard
 

package/squads/squad-commercial/tasks/coordinate-revenue-cycle.md

@@ -76,11 +76,11 @@ NRR > 100% = right side compensates for CAC
 ### 4. Cross-Squad Coordination
 | Dependency | From Squad | Status | SLA |
 |-----------|-----------|--------|-----|
-| Funnel content | @content-intelligence | | Weekly |
-| Landing pages | @digital-experience | | Per campaign |
-| Email copy | @copywriting-persuasion | | 48h turnaround |
-| Analytics data | @growth-analytics | | Real-time |
-| Market intel | @research-intelligence | | Monthly |
+| Funnel content | @content-orqx | | Weekly |
+| Landing pages | @design-orqx | | Per campaign |
+| Email copy | @squad-copy | | 48h turnaround |
+| Analytics data | @growth-orqx | | Real-time |
+| Market intel | @research-orqx | | Monthly |
 
 ## Saida
 - Revenue cycle status report

package/squads/squad-commercial/tasks/define-icp-profile.md

@@ -37,7 +37,7 @@ Definir Ideal Customer Profile (ICP) — perfil detalhado do cliente ideal basea
 - Best customer data (highest LTV, fastest close, lowest churn)
 - CRM data and analytics
 - Sales team insights
-- Market research (from @research-intelligence)
+- Market research (from @research-orqx)
 
 ## Passos
 

package/squads/squad-commercial/tasks/design-advocacy-program.md

@@ -111,4 +111,4 @@ Tracking:
 - [ ] Advocacy ladder defined with clear asks
 - [ ] Qualification criteria objective and measurable
 - [ ] Referral tracking configured in CRM
-- [ ] Content pipeline planned with @content-intelligence
+- [ ] Content pipeline planned with @content-orqx

package/squads/squad-commercial/tasks/design-lead-magnet.md

@@ -94,7 +94,7 @@ CTA After: [Next step in funnel]
 - Value test results (5/5 required)
 - Distribution plan
 - Follow-up nurture sequence (5 emails)
-- Content creation brief (→ @content-intelligence)
+- Content creation brief (→ @content-orqx)
 
 ## Validacao
 - [ ] Passes all 5 value test criteria

package/squads/squad-commercial/tasks/design-lead-magnets.md

@@ -91,8 +91,8 @@ VALUE TEST:
 
 ## Saida
 - Lead magnet briefs per persona × stage
-- Content creation briefs (→ @content-intelligence)
-- Landing page specs (→ @digital-experience)
+- Content creation briefs (→ @content-orqx)
+- Landing page specs (→ @design-orqx)
 - Follow-up nurture sequences (→ Vault)
 
 ## Validacao

package/squads/squad-commercial/tasks/manage-commercial-handoffs.md

@@ -72,11 +72,11 @@ handoff:
 ### 3. Cross-Squad Handoff Map
 | Direction | Squad | What Flows | Frequency |
 |-----------|-------|-----------|-----------|
-| IN | @growth-analytics | Lead data, attribution | Real-time |
-| IN | @content-intelligence | Funnel content assets | Per campaign |
-| IN | @copywriting-persuasion | Proposal copy, email scripts | Per project |
-| OUT | @product-systems | Feature requests, NPS data | Monthly |
-| OUT | @operations-hub | Process requirements | Quarterly |
+| IN | @growth-orqx | Lead data, attribution | Real-time |
+| IN | @content-orqx | Funnel content assets | Per campaign |
+| IN | @squad-copy | Proposal copy, email scripts | Per project |
+| OUT | @product-orqx | Feature requests, NPS data | Monthly |
+| OUT | @eng-orqx | Process requirements | Quarterly |
 
 ### 4. Handoff Quality Audit
 | Metric | Target | Current |

package/squads/squad-commercial/tasks/map-content-to-funnel.md

@@ -31,11 +31,11 @@ Checklist:
 - **Complexity:** Standard
 
 ## Objetivo
-Mapear conteudo existente e necessario para cada estagio do funil — identificar gaps de conteudo e criar briefs para @content-intelligence preencher.
+Mapear conteudo existente e necessario para cada estagio do funil — identificar gaps de conteudo e criar briefs para @content-orqx preencher.
 
 ## Entrada
 - Funnel map (from map-full-funnel)
-- Content inventory (from @content-intelligence)
+- Content inventory (from @content-orqx)
 - Buyer personas
 - Content performance data
 
@@ -69,7 +69,7 @@ Mapear conteudo existente e necessario para cada estagio do funil — identifica
 |-------------|-------|----------------|----------------|-------------------|-------------------|
 | | | | | R$ | R$ |
 
-### 4. Content Briefs for Gaps (→ @content-intelligence)
+### 4. Content Briefs for Gaps (→ @content-orqx)
 ```
 CONTENT BRIEF
 
@@ -89,7 +89,7 @@ Deadline: [Date]
 ## Saida
 - Content-to-funnel matrix (complete)
 - Gap analysis with priorities
-- Content briefs for gaps (→ @content-intelligence)
+- Content briefs for gaps (→ @content-orqx)
 - Content performance by funnel impact report
 
 ## Validacao

package/squads/squad-commercial/tasks/run-productization-sprint.md

@@ -106,9 +106,9 @@ Step 6: EXCEPTIONS — What happens with edge cases
 | Effective rate | R$/hour | R$/hour |
 
 ### 5. Go-to-Market Checklist
-- [ ] Landing page created (→ @digital-experience)
+- [ ] Landing page created (→ @design-orqx)
 - [ ] Sales script for this offer (→ Edge)
-- [ ] Case study from pilot (→ @content-intelligence)
+- [ ] Case study from pilot (→ @content-orqx)
 - [ ] CRM pipeline configured (→ Vault)
 - [ ] Nurture sequence for this ICP (→ Cascade)
 - [ ] Pricing and proposal template (→ Mint)

package/squads/squad-content/README.md

@@ -2,6 +2,12 @@
 
 > Squad de classe mundial para inteligencia de conteudo: deteccao de sinais, planejamento editorial, producao em escala com Espinha Dorsal (tese-mecanismo-prova-direcao), adaptacao nativa por plataforma com Template Contract System, auditoria de qualidade e medicao de performance.
 
+<!-- gen:start -->
+| camada | agentes | tasks | KBs | workflows | templates | checklists |
+|---|---|---|---|---|---|---|
+| iron 7 · xq 0 | 7 | 90 | 30 | 6 | 7 | 3 |
+<!-- gen:end -->
+
 ## Visao Geral
 
 | Metrica | Quantidade |
@@ -25,7 +31,16 @@
 
 ## Ativacao
 
-```bash
+Você entra por aqui, pedindo em português ao Claude Code:
+
+```
+"usa o iron-content"
+```
+
+Os nomes com `@` abaixo são **papéis internos** deste squad — quem os aciona é o
+orquestrador, não você. Não são comandos de barra nem menções que você digita.
+
+```
 # Via orquestrador (recomendado)
 @content-orqx
 
@@ -87,11 +102,8 @@
 
 ## Integracao com Core Agents
 
-Este squad trabalha com o framework SINAPSE core:
-- @architect (Aria) para decisoes tecnicas
-- @developer (Dex) para implementacao
-- @quality-gate (Quinn) para validacao de qualidade
+Este squad é orquestrado pelo `iron-ceo`, que abre o orquestrador do squad em `~/.iron/<squad>/agents/<squad>-orqx.md`.
 
 ---
 
-*Parte do ecossistema SINAPSE-AI — 18 squads, 186 agentes*
+Parte do ecossistema Iron Edge

package/squads/squad-content/agents/content-analyst.md

@@ -1,3 +1,12 @@
+---
+id: content-analyst
+layer: iron
+role: specialist
+orchestrated_by: content-orqx
+squad: squad-content
+model: sonnet
+---
+
 # content-analyst — Lens
 
 ```yaml

package/squads/squad-content/agents/content-engineer.md

@@ -1,3 +1,12 @@
+---
+id: content-engineer
+layer: iron
+role: specialist
+orchestrated_by: content-orqx
+squad: squad-content
+model: sonnet
+---
+
 # content-engineer — Arc
 
 ```yaml
@@ -79,7 +88,7 @@ persona:
 
     - trigger: "Blog article precisa ser escrito"
       action: >
-        Estrutura de blog: 1) Consultar SEO inputs de growth-analytics (keywords,
+        Estrutura de blog: 1) Consultar SEO inputs de squad-growth (keywords,
         search intent), 2) Espinha Dorsal como base, 3) Heading hierarchy
         (H1→H2→H3) alinhada com pillar-cluster model, 4) Introducao com hook +
         promessa de valor, 5) Secoes com profundidade progressiva, 6) Conclusao

package/squads/squad-content/agents/content-governor.md

@@ -1,3 +1,12 @@
+---
+id: content-governor
+layer: iron
+role: specialist
+orchestrated_by: content-orqx
+squad: squad-content
+model: sonnet
+---
+
 # content-governor — Index
 
 ```yaml
@@ -40,7 +49,7 @@ persona:
       action: >
         QA protocol: 1) Verificar template contract compliance (contagem de caracteres
         por campo, numero de slides/blocos), 2) Verificar brand consistency (tom de
-        voz alinhado com guidelines do brand-system), 3) Verificar Espinha Dorsal
+        voz alinhado com guidelines do squad-brand), 3) Verificar Espinha Dorsal
         (tese clara, mecanismo solido, prova presente, direcao definida),
         4) Verificar regras de escrita (impessoal, causal, sem metalinguagem),
         5) Scoring: cada item 0-5, media minima 4.0 para PASS.