sinapse-ai 1.19.2 → 1.20.0

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

@@ -1,8 +1,8 @@
-# content-orqx — Nexus
+# content-orqx — Bulletin
 
 ```yaml
 agent:
-  name: "Nexus"
+  name: "Bulletin"
   id: "squad-content/content-orqx"
   title: "Content Pipeline Orchestrator"
   icon: "🔗"
@@ -13,16 +13,16 @@ persona_profile:
     tone: directive
     greeting_levels:
       minimal: "🔗 content-orqx ready"
-      named: "🔗 Nexus (Conductor) ready to orchestrate the content pipeline!"
-      archetypal: "🔗 Nexus the Conductor — every piece of content starts with intention, ends with impact."
-    signature_closing: "— Nexus, orquestrando o pipeline 🔗"
+      named: "🔗 Bulletin (Conductor) ready to orchestrate the content pipeline!"
+      archetypal: "🔗 Bulletin the Conductor — every piece of content starts with intention, ends with impact."
+    signature_closing: "— Bulletin, orquestrando o pipeline 🔗"
 
 persona:
   role: "Content Pipeline Orchestrator — coordena todo o fluxo de deteccao, producao, publicacao e analise"
   identity: >
     Maestro que ve o pipeline completo de conteudo como uma orquestra: cada agente
     e um instrumentista, cada task e uma partitura, cada workflow e um movimento.
-    Nexus nao cria conteudo — garante que conteudo certo seja criado pelo agente
+    Bulletin nao cria conteudo — garante que conteudo certo seja criado pelo agente
     certo, no momento certo, com o input certo. Prioriza, distribui, desbloqueia
     gargalos e mantem o ritmo editorial.
   core_principles:

package/squads/squad-content/agents/editorial-strategist.md

@@ -65,7 +65,7 @@ persona:
       action: >
         Planejamento de sprint: 1) Selecionar temas do calendario para o periodo,
         2) Cruzar com sinais recentes do Radar, 3) Definir formato e plataforma
-        por peca, 4) Estimar esforco, 5) Criar backlog priorizado para Nexus distribuir,
+        por peca, 4) Estimar esforco, 5) Criar backlog priorizado para Bulletin distribuir,
         6) Definir acceptance criteria por peca.
       rationale: "Sprint bem planejado = producao previsivel = qualidade consistente"
 
@@ -124,7 +124,7 @@ persona:
         - "Deixar 20% de slots abertos para sinais HOT"
         - "Definir formato, plataforma e profundidade por peca"
         - "Validar mix: ≥3 pilares cobertos por semana, funil equilibrado"
-        - "Entregar para Nexus para orquestracao"
+        - "Entregar para Bulletin para orquestracao"
       validation: "Calendario cobre todos os pilares, equilibra funil, alterna formatos, tem flexibilidade"
 
     - name: "content-sprint-planning"
@@ -135,7 +135,7 @@ persona:
         - "Definir formato, plataforma e template contract"
         - "Priorizar backlog por impacto x esforco"
         - "Definir acceptance criteria"
-        - "Entregar para Nexus distribuir"
+        - "Entregar para Bulletin distribuir"
       validation: "Sprint tem backlog claro, priorizado, com criteria de aceitacao"
 
 commands:
@@ -177,7 +177,7 @@ integration:
     - agent: "content-engineer (Arc)"
       when: "Plano editorial aprovado, conteudo precisa ser estruturado e escrito"
       context_passed: "temas aprovados, Espinha Dorsal por peca, formato, template contract, pilar, funil"
-    - agent: "content-orqx (Nexus)"
+    - agent: "content-orqx (Bulletin)"
       when: "Sprint planejado, pronto para execucao"
       context_passed: "backlog priorizado, assignments, deadlines, acceptance criteria"
   receives_from:
@@ -187,7 +187,7 @@ integration:
     - agent: "content-analyst (Lens)"
       when: "Feedback loop com insights de performance"
       context_expected: "pilares top/flop, formatos com melhor ROI, gaps de performance"
-    - agent: "content-orqx (Nexus)"
+    - agent: "content-orqx (Bulletin)"
       when: "Re-priorizacao necessaria ou novo request"
       context_expected: "request, urgencia, contexto"
 ```

package/squads/squad-content/agents/platform-specialist.md

@@ -201,7 +201,7 @@ integration:
     - agent: "content-engineer (Arc)"
       when: "Conteudo produzido precisa de adaptacao por plataforma"
       context_expected: "conteudo escrito, formato, Espinha Dorsal, template contract usado"
-    - agent: "content-orqx (Nexus)"
+    - agent: "content-orqx (Bulletin)"
       when: "Batch de adaptacao ou integracao de brand assets"
       context_expected: "lista de conteudos, plataformas-alvo, template contracts"
 ```

package/squads/squad-content/agents/signal-intelligence.md

@@ -46,7 +46,7 @@ persona:
       action: >
         Rotina matinal: 1) Varrer fontes configuradas (redes sociais, portais, newsletters),
         2) Aplicar filtro de relevancia (pilar match + setor match), 3) Classificar
-        temperatura de cada sinal, 4) Se HOT: alerta imediato para Nexus,
+        temperatura de cada sinal, 4) Se HOT: alerta imediato para Bulletin,
         5) Se WARM: adicionar ao briefing semanal, 6) Se COLD: arquivar para referencia.
       rationale: "Consistencia diaria previne perda de oportunidades time-sensitive"
 
@@ -105,7 +105,7 @@ persona:
         - "Filtrar por relevancia (pilar match + setor)"
         - "Classificar temperatura: HOT (acao imediata), WARM (briefing), COLD (arquivo)"
         - "Calcular SPV para sinais HOT e WARM"
-        - "Alertar Nexus se HOT"
+        - "Alertar Bulletin se HOT"
         - "Registrar todos os sinais no log diario"
       validation: "Todos os sinais relevantes classificados e encaminhados corretamente"
 
@@ -163,14 +163,14 @@ knowledge_bases:
 
 integration:
   delegates_to:
-    - agent: "content-orqx (Nexus)"
+    - agent: "content-orqx (Bulletin)"
       when: "Sinal HOT detectado que precisa de acao imediata"
       context_passed: "sinal classificado, SPV score, janela de oportunidade, pilar, formato sugerido"
     - agent: "editorial-strategist (North)"
       when: "Briefing semanal pronto ou sinal WARM precisa de planejamento"
       context_passed: "briefing curado, sinais rankeados por SPV, mapeamento pilar-funil"
   receives_from:
-    - agent: "content-orqx (Nexus)"
+    - agent: "content-orqx (Bulletin)"
       when: "Precisa iniciar monitoramento ou ajustar fontes"
       context_expected: "pilares editoriais, fontes prioritarias, cliente/projeto"
     - agent: "editorial-strategist (North)"

package/squads/squad-content/checklists/editorial-planning-checklist.md

@@ -68,4 +68,4 @@ Aplicar apos planejamento editorial (North) e antes de iniciar producao (Arc). G
 
 ---
 
-*Checklist operado por: editorial-strategist (North) + content-orqx (Nexus)*
+*Checklist operado por: editorial-strategist (North) + content-orqx (Bulletin)*

package/squads/squad-content/checklists/onboarding-setup-checklist.md

@@ -79,7 +79,7 @@ Aplicar durante onboarding de novo cliente. Todos os items devem ser concluidos
 
 - [ ] **Calendario editorial**: Primeiro mes planejado?
 - [ ] **Sprint 1**: Pecas definidas, briefs criados?
-- [ ] **Pipeline configurado**: Nexus orquestrando?
+- [ ] **Pipeline configurado**: Bulletin orquestrando?
 
 ---
 
@@ -100,5 +100,5 @@ Aplicar durante onboarding de novo cliente. Todos os items devem ser concluidos
 
 ---
 
-*Checklist operado por: content-orqx (Nexus)*
+*Checklist operado por: content-orqx (Bulletin)*
 *Workflow de referencia: onboarding-content-cycle.yaml*

package/squads/squad-content/knowledge-base/ai-native-content-loop.md

@@ -1,7 +1,7 @@
 # AI-Native Content Loop — Canon Playbook
 
 > **Status:** Canon (squad-content v2.0)
-> **Owner:** content-orqx (Nexus) with cross-agent collaboration
+> **Owner:** content-orqx (Bulletin) with cross-agent collaboration
 > **Created:** 2026-04-12 for Story fw-v2.4
 > **Relationship to existing KBs:** Builds on `content-spine-engine.md`, `ai-leverage-content-framework.md`, `content-measurement-framework.md` and `ai-content-production.md`. This KB is the **canonical end-to-end pipeline** — the other KBs are mechanisms inside phases of this loop.
 
@@ -95,7 +95,7 @@ The loop is **closed** on purpose. Phase 6 (Retrofeed) is what turns a one-shot
 
 | Field | Value |
 |-------|-------|
-| **Lead agent** | `content-orqx` (Nexus) as coordinator; updates flow to Radar (signal tuning), North (pillar/calendar adjustment), Arc (prompt library update), Morph (template contract refinement), Index (preference log) |
+| **Lead agent** | `content-orqx` (Bulletin) as coordinator; updates flow to Radar (signal tuning), North (pillar/calendar adjustment), Arc (prompt library update), Morph (template contract refinement), Index (preference log) |
 | **Inputs** | Phase 5 performance dataset, hypotheses that produced each piece, prompt versions used |
 | **Outputs** | Updated signal-quality scoring weights, refined editorial pillars, refreshed AI prompt library, updated template contracts, updated preferences/ log for the client |
 | **Tool stack** | `generate-retrofeed-insights` task, preference log template, `ai-content-production.md` prompt library versioning |

package/squads/squad-content/knowledge-base/content-governance-principles.md

@@ -31,7 +31,7 @@ Preferencias do cliente, padroes de performance e insights de audiencia sao docu
 
 ## Matriz RACI
 
-| Atividade | Arc (Produz) | Morph (Adapta) | Index (Valida) | Nexus (Orquestra) |
+| Atividade | Arc (Produz) | Morph (Adapta) | Index (Valida) | Bulletin (Orquestra) |
 |-----------|:-----------:|:--------------:|:--------------:|:-----------------:|
 | Produzir conteudo | R | C | I | A |
 | Adaptar por plataforma | C | R | I | A |
@@ -48,7 +48,7 @@ R=Responsible, A=Accountable, C=Consulted, I=Informed
 ```
 Nivel 1 (Padrao): Arc → Index (1 gate) → Publicacao
 Nivel 2 (Sensivel): Arc → Index → Review Adicional → Publicacao
-Nivel 3 (Crise): Arc → Index → Nexus → Stakeholder → Publicacao
+Nivel 3 (Crise): Arc → Index → Bulletin → Stakeholder → Publicacao
 ```
 
 ---

package/squads/squad-content/knowledge-base/cross-squad-integration-protocol.md

@@ -23,7 +23,7 @@
 | **growth-analytics** | Dados de performance de conteudo, ROI | Lens (relatorio) |
 | **commercial-systems** | Conteudo de produto, cases, materiais de venda | Arc (produz) |
 | **community-engagement** | Conteudo para social, UGC curado, temas para comunidade | Arc + Morph (produzem) |
-| **copywriting-persuasion** | Briefs de conteudo que precisam de copy persuasiva | North (brief), Nexus (handoff) |
+| **copywriting-persuasion** | Briefs de conteudo que precisam de copy persuasiva | North (brief), Bulletin (handoff) |
 | **brand-system** | Feedback de campo sobre brand voice em acao | Lens (dados), Index (inconsistencias) |
 
 ---

package/squads/squad-content/knowledge-base/signal-intelligence-v2.md

@@ -1,7 +1,7 @@
 # Signal Intelligence v2 — 2026 Sources + Classification Canon
 
 > **Status:** Canon (squad-content v2.0) — ADDITIVE companion to `signal-detection-methods.md` v1
-> **Owner:** signal-intelligence (Radar) — primary; content-orqx (Nexus) — curator
+> **Owner:** signal-intelligence (Radar) — primary; content-orqx (Bulletin) — curator
 > **Created:** 2026-04-12 for Story fw-v2.4
 > **Explicit relationship:** Does NOT replace `signal-detection-methods.md`. v1 remains canonical for foundational definitions. v2 adds the 2026 source landscape, the signal classification taxonomy, routing rules and a quality-scoring model that did not exist in v1.
 

package/squads/squad-content/knowledge-base/task-ownership-map.md

@@ -1,7 +1,7 @@
 # Task Ownership Map — squad-content v2.0
 
 > **Status:** Canon (squad-content v2.0)
-> **Owner:** content-orqx (Nexus) — curator; all 7 agents contribute via audit
+> **Owner:** content-orqx (Bulletin) — curator; all 7 agents contribute via audit
 > **Created:** 2026-04-12 for Story fw-v2.4
 > **Source of truth:** Disk reality of `squads/squad-content/tasks/` at 2026-04-12 (90 task files)
 
@@ -33,7 +33,7 @@ A task can only have ONE primary. Up to TWO secondaries.
 
 ## 3. Full Ownership Matrix (90 tasks)
 
-### 3.1 Orchestrator — content-orqx (Nexus) — 5 primary tasks
+### 3.1 Orchestrator — content-orqx (Bulletin) — 5 primary tasks
 
 | Task | Primary | Secondary | Phase in loop |
 |------|---------|-----------|--------------|
@@ -176,7 +176,7 @@ Verification + Batch (2):
 
 | Agent | Primary Count | Phase Coverage | Load Category |
 |-------|--------------|----------------|---------------|
-| content-orqx (Nexus) | 5 | cross-phase | Coordinator (intentionally light) |
+| content-orqx (Bulletin) | 5 | cross-phase | Coordinator (intentionally light) |
 | signal-intelligence (Radar) | 10 | Phase 1 | Balanced |
 | editorial-strategist (North) | 10 | Pre-phase / Phase 6 | Balanced |
 | content-engineer (Arc) | 25 | Phase 2 | **OVER-LOADED** |
@@ -195,9 +195,9 @@ Arc carries 25 primary tasks — nearly 2x the next-heaviest agent. This is a le
 
 **Open question for a future story:** should Arc split into `structure-engineer` (design-* + structure-*) + `content-writer` (write-* family)? This is a candidate for fw-v3 or a dedicated refactoring story. Logged here, not executed here.
 
-### 5.2 content-orqx (Nexus) is intentionally light
+### 5.2 content-orqx (Bulletin) is intentionally light
 
-5 tasks is correct for the orchestrator — Nexus delegates and coordinates, never executes write-* or analyze-*. Any attempt to grow Nexus's primary count is a smell.
+5 tasks is correct for the orchestrator — Bulletin delegates and coordinates, never executes write-* or analyze-*. Any attempt to grow Bulletin's primary count is a smell.
 
 ### 5.3 Phase 6 (Retrofeed) is thin
 

package/squads/squad-content/squad.yaml

@@ -155,7 +155,7 @@ core_concepts:
 
 components:
   agents:
-    - content-orqx.md      # Nexus — Conductor (5 tasks)
+    - content-orqx.md      # Bulletin — Conductor (5 tasks)
     - signal-intelligence.md       # Radar — Scout (9 tasks)
     - editorial-strategist.md      # North — Navigator (10 tasks)
     - content-engineer.md          # Truss — Engineer (25 tasks)
@@ -168,7 +168,7 @@ components:
 # ══════════════════════════════════════════════════════════════════════════════
 
   tasks:
-    # ── Orchestrator (Nexus) — 5 tasks ──
+    # ── Orchestrator (Bulletin) — 5 tasks ──
     - orchestrate-content-pipeline.md
     - manage-content-sprint.md
     - coordinate-cross-squad.md

package/squads/squad-content/tasks/alert-opportunity-windows.md

@@ -34,11 +34,11 @@ Checklist:
 | Campo | Valor |
 |-------|-------|
 | **Agent** | signal-intelligence (Radar) |
-| **Co-agents** | content-orqx (Nexus) |
+| **Co-agents** | content-orqx (Bulletin) |
 | **Trigger** | Sinal HOT detectado com janela curta |
 | **Input** | Sinal classificado como HOT (SPV >= 4, janela < 24h) |
-| **Output** | Alerta formatado para Nexus com sinal, janela e recomendacao |
-| **Handoff** | → content-orqx (Nexus) para triage-urgent-signal |
+| **Output** | Alerta formatado para Bulletin com sinal, janela e recomendacao |
+| **Handoff** | → content-orqx (Bulletin) para triage-urgent-signal |
 | **Complexity** | simple |
 
 ---
@@ -57,8 +57,8 @@ Verificar: SPV >= 4? Janela < 24h? Conecta com pilares? Se todos sim: emitir ale
 ### Step 2: Formatar Alerta
 Alerta contém: sinal (1 frase), SPV score, janela estimada, pilar conectado, formato sugerido, angulo recomendado.
 
-### Step 3: Enviar para Nexus
-Entregar alerta para Nexus acionar triage-urgent-signal.
+### Step 3: Enviar para Bulletin
+Entregar alerta para Bulletin acionar triage-urgent-signal.
 
 ### Step 4: Handoff
 
@@ -66,5 +66,5 @@ Entregar alerta para Nexus acionar triage-urgent-signal.
 handoff:
   artifact: "opportunity-alert-{signal}.md"
   context: "Alerta HOT: {sinal}, SPV {score}, janela {horas}h"
-  next: "content-orqx (Nexus) para triage-urgent-signal"
+  next: "content-orqx (Bulletin) para triage-urgent-signal"
 ```

package/squads/squad-content/tasks/analyze-content-performance.md

@@ -38,7 +38,7 @@ Checklist:
 | **Trigger** | Semanal (report rapido), mensal (deep dive), trimestral (analise completa) |
 | **Input** | Metricas de todas as plataformas, KPIs definidos, historico de performance |
 | **Output** | Report de performance com insights, tendencias e recomendacoes |
-| **Handoff** | → editorial-strategist (North) e content-orqx (Nexus) |
+| **Handoff** | → editorial-strategist (North) e content-orqx (Bulletin) |
 | **Complexity** | complex |
 
 ---
@@ -75,5 +75,5 @@ De top + bottom: quais insights geram acao? "Carrosseis educativos com hook de d
 handoff:
   artifact: "performance-report-{period}.md"
   context: "Performance: {N} pecas analisadas, top performer '{top}', {R} recomendacoes, KPIs {status}"
-  next: "editorial-strategist (North) para ajustar estrategia, content-orqx (Nexus) para proxima sprint"
+  next: "editorial-strategist (North) para ajustar estrategia, content-orqx (Bulletin) para proxima sprint"
 ```

package/squads/squad-content/tasks/batch-content-production.md

@@ -34,7 +34,7 @@ Checklist:
 | Campo | Valor |
 |-------|-------|
 | **Agent** | content-engineer (Arc) |
-| **Co-agents** | content-orqx (Nexus), platform-specialist (Morph) |
+| **Co-agents** | content-orqx (Bulletin), platform-specialist (Morph) |
 | **Trigger** | Sprint semanal ou producao em volume |
 | **Input** | Lista de briefs, Espinhas Dorsais pre-definidas, Template Contracts |
 | **Output** | Lote de pecas produzidas e validadas |

package/squads/squad-content/tasks/benchmark-against-competitors.md

@@ -38,7 +38,7 @@ Checklist:
 | **Trigger** | Mensal ou trimestral |
 | **Input** | Dados proprios, dados publicos de concorrentes, relatorios do Radar |
 | **Output** | Benchmark comparativo com posicao relativa e oportunidades |
-| **Handoff** | → editorial-strategist (North), content-orqx (Nexus) |
+| **Handoff** | → editorial-strategist (North), content-orqx (Bulletin) |
 | **Complexity** | medium |
 
 ---

package/squads/squad-content/tasks/coordinate-cross-squad.md

@@ -33,7 +33,7 @@ Checklist:
 
 | Campo | Valor |
 |-------|-------|
-| **Agent** | content-orqx (Nexus) |
+| **Agent** | content-orqx (Bulletin) |
 | **Co-agents** | Agentes das squads parceiras |
 | **Trigger** | Necessidade de input cross-squad ou entrega de output |
 | **Input** | Necessidade identificada (brand guidelines, SEO data, copy optimization, etc.) |

package/squads/squad-content/tasks/create-content-governance.md

@@ -34,7 +34,7 @@ Checklist:
 | Campo | Valor |
 |-------|-------|
 | **Agent** | content-governor (Index) |
-| **Co-agents** | content-orqx (Nexus) |
+| **Co-agents** | content-orqx (Bulletin) |
 | **Trigger** | Setup de novo projeto ou revisao anual |
 | **Input** | Escopo do projeto, equipe, plataformas, regulacoes do setor |
 | **Output** | Documento de governanca com politicas, processos e responsabilidades |

package/squads/squad-content/tasks/create-editorial-calendar.md

@@ -34,7 +34,7 @@ Checklist:
 | Campo | Valor |
 |-------|-------|
 | **Agent** | editorial-strategist (North) |
-| **Co-agents** | content-orqx (Nexus), platform-specialist (Morph) |
+| **Co-agents** | content-orqx (Bulletin), platform-specialist (Morph) |
 | **Trigger** | Apos definicao de pilares ou inicio de novo ciclo (mensal/trimestral) |
 | **Input** | Pilares editoriais, datas sazonais, frequencia por plataforma, capacidade de producao |
 | **Output** | Calendario editorial estruturado com slots, temas e distribuicao |

package/squads/squad-content/tasks/curate-ugc-signals.md

@@ -38,7 +38,7 @@ Checklist:
 | **Trigger** | Diario, integrado ao scan de sinais |
 | **Input** | Hashtags da marca, mentions, reviews, tags, reposts |
 | **Output** | UGC curado com classificacao de qualidade e potencial de amplificacao |
-| **Handoff** | → content-orqx (Nexus) para decisao de amplificacao |
+| **Handoff** | → content-orqx (Bulletin) para decisao de amplificacao |
 | **Complexity** | medium |
 
 ---
@@ -75,5 +75,5 @@ Resumo semanal: melhores UGCs por categoria, tendencias de criacao da audiencia,
 handoff:
   artifact: "ugc-curation-{date}.md"
   context: "UGC curado: {N} pecas, {R} para repost, {C} para co-criacao, sentimento {positivo/neutro/negativo}"
-  next: "content-orqx (Nexus) para decisao de amplificacao e flag-content-for-amplification"
+  next: "content-orqx (Bulletin) para decisao de amplificacao e flag-content-for-amplification"
 ```

package/squads/squad-content/tasks/define-big-idea.md

@@ -34,7 +34,7 @@ Checklist:
 | Campo | Valor |
 |-------|-------|
 | **Agent** | editorial-strategist (North) |
-| **Co-agents** | content-orqx (Nexus) |
+| **Co-agents** | content-orqx (Bulletin) |
 | **Trigger** | Onboarding de novo cliente ou revisao estrategica trimestral |
 | **Input** | Brand voice (do squad brand-system), posicionamento, publico-alvo, objetivos de negocio |
 | **Output** | Big Idea documentada com narrativa-mestre e territorios tematicos |

package/squads/squad-content/tasks/define-content-kpis.md

@@ -34,7 +34,7 @@ Checklist:
 | Campo | Valor |
 |-------|-------|
 | **Agent** | editorial-strategist (North) |
-| **Co-agents** | content-analyst (Lens), content-orqx (Nexus) |
+| **Co-agents** | content-analyst (Lens), content-orqx (Bulletin) |
 | **Trigger** | Onboarding de novo cliente ou revisao trimestral |
 | **Input** | Objetivos de negocio, capacidade de medicao, plataformas ativas |
 | **Output** | Framework de KPIs com metricas, metas e frequencia de medicao |

package/squads/squad-content/tasks/flag-content-for-amplification.md

@@ -38,7 +38,7 @@ Checklist:
 | **Trigger** | Pos-publicacao quando conteudo mostra sinais de performance acima da media |
 | **Input** | Metricas de performance inicial (primeiras 24-48h), benchmarks |
 | **Output** | Lista de conteudo flagged com recomendacao de amplificacao |
-| **Handoff** | → content-orqx (Nexus) para decisao de investimento |
+| **Handoff** | → content-orqx (Bulletin) para decisao de investimento |
 | **Complexity** | simple |
 
 ---
@@ -69,5 +69,5 @@ Para BOOST: estimativa de alcance adicional por investimento. Para REPOST: poten
 handoff:
   artifact: "amplification-flags-{date}.md"
   context: "Flagged: {N} pecas para amplificacao, tipos: {B} boost, {R} repost, {C} collab"
-  next: "content-orqx (Nexus) para decisao de investimento"
+  next: "content-orqx (Bulletin) para decisao de investimento"
 ```

package/squads/squad-content/tasks/generate-content-report.md

@@ -34,11 +34,11 @@ Checklist:
 | Campo | Valor |
 |-------|-------|
 | **Agent** | content-analyst (Lens) |
-| **Co-agents** | content-orqx (Nexus) |
+| **Co-agents** | content-orqx (Bulletin) |
 | **Trigger** | Mensal (report padrao) ou sob demanda |
 | **Input** | Todas as metricas e analises do periodo |
 | **Output** | Relatorio executivo com metricas, insights e recomendacoes |
-| **Handoff** | → content-orqx (Nexus), stakeholders |
+| **Handoff** | → content-orqx (Bulletin), stakeholders |
 | **Complexity** | medium |
 
 ---
@@ -72,5 +72,5 @@ Executivos: 1 pagina de executive summary. Equipe operacional: detalhamento comp
 handoff:
   artifact: "content-report-{period}.md"
   context: "Report: {periodo}, {N} metricas, {D} destaques, {R} recomendacoes"
-  next: "content-orqx (Nexus) para distribuicao e stakeholders"
+  next: "content-orqx (Bulletin) para distribuicao e stakeholders"
 ```

package/squads/squad-content/tasks/manage-content-sprint.md

@@ -33,7 +33,7 @@ Checklist:
 
 | Campo | Valor |
 |-------|-------|
-| **Agent** | content-orqx (Nexus) |
+| **Agent** | content-orqx (Bulletin) |
 | **Co-agents** | editorial-strategist (North), content-engineer (Arc) |
 | **Trigger** | Inicio de sprint editorial |
 | **Input** | Sprint plan de North, backlog priorizado |

package/squads/squad-content/tasks/measure-content-roi.md

@@ -34,11 +34,11 @@ Checklist:
 | Campo | Valor |
 |-------|-------|
 | **Agent** | content-analyst (Lens) |
-| **Co-agents** | content-orqx (Nexus) |
+| **Co-agents** | content-orqx (Bulletin) |
 | **Trigger** | Mensal ou trimestral |
 | **Input** | Custos de producao, metricas de conversao, dados de revenue |
 | **Output** | Report de ROI com custo por lead, custo por conversao, valor gerado |
-| **Handoff** | → content-orqx (Nexus), editorial-strategist (North) |
+| **Handoff** | → content-orqx (Bulletin), editorial-strategist (North) |
 | **Complexity** | complex |
 
 ---
@@ -72,5 +72,5 @@ ROI por formato (blog gera mais leads? Reels geram mais awareness?), ROI por pil
 handoff:
   artifact: "content-roi-{period}.md"
   context: "ROI: {X}%, CPL {valor}, revenue atribuida {valor}, melhor formato {formato}"
-  next: "content-orqx (Nexus) e editorial-strategist (North) para ajustar investimento"
+  next: "content-orqx (Bulletin) e editorial-strategist (North) para ajustar investimento"
 ```

package/squads/squad-content/tasks/orchestrate-content-pipeline.md

@@ -33,7 +33,7 @@ Checklist:
 
 | Campo | Valor |
 |-------|-------|
-| **Agent** | content-orqx (Nexus) |
+| **Agent** | content-orqx (Bulletin) |
 | **Co-agents** | Todos os agentes do squad |
 | **Trigger** | Inicio de sprint ou novo projeto |
 | **Input** | Plano editorial de North, sinais do Radar, status do pipeline |
@@ -45,7 +45,7 @@ Checklist:
 
 ## Fundamentacao
 
-Orquestracao e o que transforma agentes individuais em sistema coeso. Sem coordenacao explicita, o pipeline fragmenta: Radar detecta sinais que North nao prioriza, Arc produz conteudo que Morph nao consegue adaptar a tempo, Index valida sem contexto. Nexus garante que o pipeline opere como unidade sincronizada, nao como colecao de agentes independentes. Referencia: Halvorson Content Strategy Quad — Workflow como uma das 4 dimensoes criticas.
+Orquestracao e o que transforma agentes individuais em sistema coeso. Sem coordenacao explicita, o pipeline fragmenta: Radar detecta sinais que North nao prioriza, Arc produz conteudo que Morph nao consegue adaptar a tempo, Index valida sem contexto. Bulletin garante que o pipeline opere como unidade sincronizada, nao como colecao de agentes independentes. Referencia: Halvorson Content Strategy Quad — Workflow como uma das 4 dimensoes criticas.
 
 ---
 

package/squads/squad-content/tasks/plan-content-sprint.md

@@ -34,11 +34,11 @@ Checklist:
 | Campo | Valor |
 |-------|-------|
 | **Agent** | editorial-strategist (North) |
-| **Co-agents** | content-orqx (Nexus), content-engineer (Arc) |
+| **Co-agents** | content-orqx (Bulletin), content-engineer (Arc) |
 | **Trigger** | Inicio de cada semana ou sprint |
 | **Input** | Calendario editorial, sinais da semana (Radar), capacidade disponivel |
 | **Output** | Sprint planejado com pecas atribuidas, prazos e prioridades |
-| **Handoff** | → content-orqx (Nexus) para orquestracao da producao |
+| **Handoff** | → content-orqx (Bulletin) para orquestracao da producao |
 | **Complexity** | medium |
 
 ---
@@ -72,5 +72,5 @@ Compilar sprint com: coluna backlog, em producao, em revisao, aprovado, publicad
 handoff:
   artifact: "content-sprint-{week}.md"
   context: "Sprint planejado: {N} pecas, {P} plataformas, {H} sinais incorporados, capacidade {X}%"
-  next: "content-orqx (Nexus) para iniciar producao e orquestrar pipeline"
+  next: "content-orqx (Bulletin) para iniciar producao e orquestrar pipeline"
 ```

package/squads/squad-content/tasks/predict-content-performance.md

@@ -37,7 +37,7 @@ Checklist:
 | **Trigger** | Pre-publicacao (opcional, para priorizacao) |
 | **Input** | Conteudo finalizado, historico de performance, padroes identificados |
 | **Output** | Score preditivo com range estimado de performance |
-| **Handoff** | → content-orqx (Nexus) para priorizacao |
+| **Handoff** | → content-orqx (Bulletin) para priorizacao |
 | **Complexity** | medium |
 
 ---
@@ -68,5 +68,5 @@ Score 1-10 com confianca (alta, media, baixa). Range estimado: engagement rate e
 handoff:
   artifact: "performance-prediction-{peca}.md"
   context: "Previsao: score {score}/10, range {min}-{max}%, confianca {nivel}"
-  next: "content-orqx (Nexus) para priorizacao de publicacao e investimento"
+  next: "content-orqx (Bulletin) para priorizacao de publicacao e investimento"
 ```

package/squads/squad-content/tasks/scan-daily-signals.md

@@ -64,7 +64,7 @@ Para cada sinal detectado: conecta com algum pilar editorial? E relevante para o
 Aplicar classificacao: HOT (janela < 24h, SPV alto), WARM (janela 7d, SPV moderado), COLD (evergreen, SPV baixo). Usar classify-signal-temperature se necessario.
 
 ### Step 5: Registrar e Encaminhar
-Registrar todos os sinais no log diario. Se HOT: alerta imediato para Nexus via alert-opportunity-windows.
+Registrar todos os sinais no log diario. Se HOT: alerta imediato para Bulletin via alert-opportunity-windows.
 
 ### Step 6: Handoff
 
@@ -72,5 +72,5 @@ Registrar todos os sinais no log diario. Se HOT: alerta imediato para Nexus via
 handoff:
   artifact: "daily-signal-log-{date}.md"
   context: "Scan diario completo: {N} sinais detectados ({HOT}/{WARM}/{COLD})"
-  next: "content-orqx (Nexus) se HOT, acumular para curate-weekly-briefing se WARM"
+  next: "content-orqx (Bulletin) se HOT, acumular para curate-weekly-briefing se WARM"
 ```

package/squads/squad-content/tasks/triage-content-requests.md

@@ -33,7 +33,7 @@ Checklist:
 
 | Campo | Valor |
 |-------|-------|
-| **Agent** | content-orqx (Nexus) |
+| **Agent** | content-orqx (Bulletin) |
 | **Co-agents** | editorial-strategist (North) |
 | **Trigger** | Novo request de conteudo (interno ou externo) |
 | **Input** | Request com descricao, urgencia e contexto |

package/squads/squad-content/tasks/triage-urgent-signal.md

@@ -33,7 +33,7 @@ Checklist:
 
 | Campo | Valor |
 |-------|-------|
-| **Agent** | content-orqx (Nexus) |
+| **Agent** | content-orqx (Bulletin) |
 | **Co-agents** | signal-intelligence (Radar), content-engineer (Arc), content-governor (Index) |
 | **Trigger** | Alerta HOT do Radar com janela de oportunidade curta |
 | **Input** | Sinal HOT classificado com SPV >= 4, janela de oportunidade |

package/squads/squad-content/templates/signal-alert-template.md

@@ -56,7 +56,7 @@
 
 | Acao | Responsavel | Prazo |
 |------|------------|-------|
-| Aprovar/rejeitar sinal | Nexus | {imediato} |
+| Aprovar/rejeitar sinal | Bulletin | {imediato} |
 | Criar brief | Arc | {X horas} |
 | Produzir conteudo | Arc | {X horas} |
 | Adaptar plataforma | Morph | {X horas} |
@@ -66,4 +66,4 @@
 ---
 
 *Template operado por: signal-intelligence (Radar)*
-*Destinatario: content-orqx (Nexus)*
+*Destinatario: content-orqx (Bulletin)*

package/squads/squad-content/templates/weekly-briefing-template.md

@@ -7,7 +7,7 @@
 ## Briefing Semanal — Semana {N} ({data inicio} — {data fim})
 
 **Emitido por**: signal-intelligence (Radar)
-**Para**: editorial-strategist (North), content-orqx (Nexus)
+**Para**: editorial-strategist (North), content-orqx (Bulletin)
 
 ---
 

package/squads/squad-content/workflows/content-audit-cycle.yaml

@@ -1,7 +1,7 @@
 cadence: Trimestral
 estimated_duration: 4-8 horas
 orchestration:
-  coordinator: content-orqx (Nexus)
+  coordinator: content-orqx (Bulletin)
   deliverables:
     - content-audit-report.md (completo)
     - content-performance-report.md (metricas)

package/squads/squad-content/workflows/content-creation-cycle.yaml

@@ -1,7 +1,7 @@
 cadence: Continuo — acionado por demanda
 estimated_duration: 1-4 horas (unitario) | 4-8 horas (batch)
 orchestration:
-  coordinator: content-orqx (Nexus)
+  coordinator: content-orqx (Bulletin)
   modes:
     single:
       description: Producao unitaria — 1 peca
@@ -79,7 +79,7 @@ workflow:
         - validate-content-compliance
     - phase: 5
       name: Publication
-      agent: content-orqx (Nexus)
+      agent: content-orqx (Bulletin)
       tasks: []
       input: Conteudo aprovado
       output: Conteudo publicado
@@ -141,7 +141,7 @@ workflow:
         - validate-content-compliance
     - phase: 5
       name: Publication
-      agent: content-orqx (Nexus)
+      agent: content-orqx (Bulletin)
       tasks: []
       input: Conteudo aprovado
       output: Conteudo publicado