sinapse-ai 9.3.0 → 9.5.0

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

@@ -0,0 +1,235 @@
+# Task Ownership Map — squad-content v2.0
+
+> **Status:** Canon (squad-content v2.0)
+> **Owner:** content-orqx (Nexus) — 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)
+
+---
+
+## 1. Why This Exists
+
+squad-content is the heaviest task squad in SINAPSE (90 tasks across 7 agents). Without an explicit ownership map, tasks implicitly belong to the first agent that opened a file, which leads to:
+
+- **Ownership ambiguity** — nobody feels accountable for a given task
+- **Over-load and under-load drift** — some agents carry 25+ tasks, others carry 5
+- **Orphaned tasks** — legacy tasks with no clear owner
+- **Cross-agent duplication** — two agents quietly build parallel versions of the same capability
+
+This KB makes ownership explicit: **every task has exactly one primary agent and zero to two secondary agents.** The yaml `components.agents` block in `squads/squad-content/squad.yaml` will carry a `tasks:` field per agent reflecting this map, so both humans and the framework runtime can resolve ownership deterministically.
+
+---
+
+## 2. Ownership Definitions
+
+| Role | Responsibility |
+|------|---------------|
+| **Primary** | Owns the task: maintains it, receives the work request first, executes or delegates, accountable for output quality |
+| **Secondary** | Collaborates when the primary requests help, adds domain-specific layers (ex: content-governor adds compliance check to a write-* task), can be a reviewer but not the executor |
+
+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
+
+| Task | Primary | Secondary | Phase in loop |
+|------|---------|-----------|--------------|
+| `orchestrate-content-pipeline.md` | content-orqx | — | cross-phase |
+| `manage-content-sprint.md` | content-orqx | editorial-strategist | cross-phase |
+| `coordinate-cross-squad.md` | content-orqx | — | cross-phase |
+| `triage-content-requests.md` | content-orqx | editorial-strategist | pre-phase-1 |
+| `triage-urgent-signal.md` | content-orqx | signal-intelligence | phase 1 |
+
+### 3.2 Signal Intelligence (Radar) — 10 primary tasks
+
+| Task | Primary | Secondary | Phase |
+|------|---------|-----------|-------|
+| `scan-daily-signals.md` | signal-intelligence | — | 1 |
+| `detect-trending-topics.md` | signal-intelligence | — | 1 |
+| `map-cultural-signals.md` | signal-intelligence | editorial-strategist | 1 |
+| `curate-weekly-briefing.md` | signal-intelligence | content-orqx | 1 |
+| `monitor-competitor-content.md` | signal-intelligence | content-analyst | 1 |
+| `alert-opportunity-windows.md` | signal-intelligence | editorial-strategist | 1 |
+| `classify-signal-temperature.md` | signal-intelligence | — | 1 |
+| `map-signal-to-pillar.md` | signal-intelligence | editorial-strategist | 1 |
+| `configure-signal-sources.md` | signal-intelligence | content-orqx | 1 |
+| `curate-ugc-signals.md` | signal-intelligence | content-governor | 1 |
+
+### 3.3 Editorial Strategist (North) — 10 primary tasks
+
+| Task | Primary | Secondary | Phase |
+|------|---------|-----------|-------|
+| `define-big-idea.md` | editorial-strategist | content-orqx | pre-phase-1 |
+| `define-editorial-pillars.md` | editorial-strategist | content-orqx, signal-intelligence | pre-phase-1 |
+| `create-editorial-calendar.md` | editorial-strategist | platform-specialist | pre-phase-1 |
+| `plan-content-sprint.md` | editorial-strategist | content-orqx | pre-phase-1 |
+| `align-content-to-funnel.md` | editorial-strategist | — | pre-phase-1 |
+| `map-content-gaps.md` | editorial-strategist | content-analyst | 6 (retrofeed) |
+| `plan-seasonal-content.md` | editorial-strategist | — | pre-phase-1 |
+| `prioritize-themes.md` | editorial-strategist | content-orqx | pre-phase-1 |
+| `balance-content-mix.md` | editorial-strategist | platform-specialist | pre-phase-1 |
+| `define-content-kpis.md` | editorial-strategist | content-analyst | pre-phase-1 |
+
+### 3.4 Content Engineer (Arc) — 25 primary tasks
+
+Structure mode (11):
+
+| Task | Primary | Secondary | Phase |
+|------|---------|-----------|-------|
+| `design-content-spine.md` | content-engineer | editorial-strategist | 2 |
+| `design-narrative-arc.md` | content-engineer | — | 2 |
+| `structure-carousel-progression.md` | content-engineer | platform-specialist | 2 |
+| `structure-video-script.md` | content-engineer | platform-specialist | 2 |
+| `design-content-series.md` | content-engineer | editorial-strategist | 2 |
+| `apply-storybrand-framework.md` | content-engineer | — | 2 |
+| `design-pillar-cluster-model.md` | content-engineer | editorial-strategist | 2 |
+| `create-content-brief.md` | content-engineer | content-orqx | 2 |
+| `design-hook-system.md` | content-engineer | — | 2 |
+| `structure-argument-progression.md` | content-engineer | — | 2 |
+| `define-content-depth-levels.md` | content-engineer | editorial-strategist | 2 |
+
+Write mode (12):
+
+| Task | Primary | Secondary | Phase |
+|------|---------|-----------|-------|
+| `write-carousel-content.md` | content-engineer | platform-specialist | 2 |
+| `write-instagram-caption.md` | content-engineer | platform-specialist | 2 |
+| `write-linkedin-post.md` | content-engineer | platform-specialist | 2 |
+| `write-blog-article.md` | content-engineer | — | 2 |
+| `write-video-script.md` | content-engineer | platform-specialist | 2 |
+| `write-reel-script.md` | content-engineer | platform-specialist | 2 |
+| `write-newsletter-editorial.md` | content-engineer | editorial-strategist | 2 |
+| `write-thread-content.md` | content-engineer | platform-specialist | 2 |
+| `write-opinion-post.md` | content-engineer | editorial-strategist | 2 |
+| `write-case-study.md` | content-engineer | content-analyst | 2 |
+| `write-educational-content.md` | content-engineer | — | 2 |
+| `write-product-content.md` | content-engineer | editorial-strategist | 2 |
+
+Verification + Batch (2):
+
+| Task | Primary | Secondary | Phase |
+|------|---------|-----------|-------|
+| `verify-algorithmic-hooks.md` | content-engineer | platform-specialist | 3/4 |
+| `batch-content-production.md` | content-engineer | platform-specialist | 2 |
+
+### 3.5 Platform Specialist (Morph) — 17 primary tasks
+
+| Task | Primary | Secondary | Phase |
+|------|---------|-----------|-------|
+| `adapt-for-instagram-feed.md` | platform-specialist | content-engineer | 4 |
+| `adapt-for-instagram-stories.md` | platform-specialist | content-engineer | 4 |
+| `adapt-for-instagram-reels.md` | platform-specialist | content-engineer | 4 |
+| `adapt-for-linkedin.md` | platform-specialist | content-engineer | 4 |
+| `adapt-for-blog-seo.md` | platform-specialist | content-engineer | 4 |
+| `adapt-for-tiktok.md` | platform-specialist | content-engineer | 4 |
+| `adapt-for-twitter-threads.md` | platform-specialist | content-engineer | 4 |
+| `define-posting-schedule.md` | platform-specialist | editorial-strategist | 4 |
+| `create-platform-guidelines.md` | platform-specialist | content-governor | 4 |
+| `optimize-for-algorithm.md` | platform-specialist | — | 4 |
+| `design-content-atomization.md` | platform-specialist | content-engineer | 4 |
+| `register-template-contract.md` | platform-specialist | content-governor | 4 |
+| `update-template-specs.md` | platform-specialist | content-governor | 4 |
+| `adapt-content-language.md` | platform-specialist | — | 4 |
+| `batch-platform-adaptation.md` | platform-specialist | content-engineer | 4 |
+| `flag-content-for-amplification.md` | platform-specialist | content-analyst | 4/5 |
+| `integrate-brand-visual-assets.md` | platform-specialist | — | 4 |
+
+### 3.6 Content Governor (Index) — 12 primary tasks
+
+| Task | Primary | Secondary | Phase |
+|------|---------|-----------|-------|
+| `audit-content-library.md` | content-governor | content-analyst | 6 |
+| `check-brand-consistency.md` | content-governor | — | 3 |
+| `validate-content-quality.md` | content-governor | editorial-strategist | 3 |
+| `manage-content-taxonomy.md` | content-governor | — | 6 |
+| `organize-content-archive.md` | content-governor | — | 6 |
+| `create-content-governance.md` | content-governor | content-orqx | cross-phase |
+| `define-content-standards.md` | content-governor | content-orqx | cross-phase |
+| `audit-template-compliance.md` | content-governor | platform-specialist | 4/6 |
+| `validate-content-compliance.md` | content-governor | — | 3 |
+| `process-content-rejection.md` | content-governor | editorial-strategist | 3 |
+| `import-existing-content-library.md` | content-governor | — | pre-phase-1 |
+| `update-content-preferences.md` | content-governor | content-analyst | 6 |
+
+### 3.7 Content Analyst (Lens) — 11 primary tasks
+
+| Task | Primary | Secondary | Phase |
+|------|---------|-----------|-------|
+| `analyze-content-performance.md` | content-analyst | — | 5 |
+| `score-content-quality.md` | content-analyst | content-governor | 5 |
+| `measure-content-roi.md` | content-analyst | — | 5 |
+| `track-engagement-patterns.md` | content-analyst | — | 5 |
+| `benchmark-against-competitors.md` | content-analyst | signal-intelligence | 5 |
+| `evaluate-eeat-compliance.md` | content-analyst | content-governor | 5 |
+| `generate-content-report.md` | content-analyst | — | 5 |
+| `identify-top-performers.md` | content-analyst | — | 5 |
+| `predict-content-performance.md` | content-analyst | — | 5 |
+| `analyze-audience-behavior.md` | content-analyst | signal-intelligence | 5 |
+| `generate-retrofeed-insights.md` | content-analyst | content-orqx, editorial-strategist | 6 |
+
+---
+
+## 4. Ownership Summary
+
+| Agent | Primary Count | Phase Coverage | Load Category |
+|-------|--------------|----------------|---------------|
+| content-orqx (Nexus) | 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** |
+| platform-specialist (Morph) | 17 | Phase 4 | High but coherent |
+| content-governor (Index) | 12 | Phase 3 + 6 | Balanced |
+| content-analyst (Lens) | 11 | Phase 5 + 6 | Balanced |
+| **Total** | **90** | All 6 | — |
+
+---
+
+## 5. Imbalance Audit
+
+### 5.1 content-engineer (Arc) is over-loaded
+
+Arc carries 25 primary tasks — nearly 2x the next-heaviest agent. This is a legitimate imbalance because Arc owns both structural design AND the full writing surface (12 write-* tasks). In v2 we document the imbalance but do **not** create a new agent in this story (see `scope_out` of fw-v2.4).
+
+**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 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.3 Phase 6 (Retrofeed) is thin
+
+Only 3 tasks are explicitly phase-6 primaries (`generate-retrofeed-insights`, `audit-content-library`, `map-content-gaps`, `update-content-preferences`). This may be a real capability gap — retrofeed automation tasks could grow in a future story.
+
+### 5.4 No orphans detected
+
+Every one of the 90 tasks has a clear primary owner. No orphaned tasks found during the audit.
+
+---
+
+## 6. How to Use This Map
+
+1. **Request routing** — When a client request hits `triage-content-requests`, the map determines which agent is invoked.
+2. **Runtime enforcement** — The yaml `components.agents[].tasks` field reflects this map for deterministic resolution by the framework.
+3. **Load balancing** — Future sprints should use the "Load Category" column to avoid bottlenecking Arc.
+4. **Onboarding** — A new operator sees at a glance which agent owns what.
+5. **Cross-agent handoffs** — When a primary needs a secondary, this map is the handshake reference.
+
+---
+
+## 7. Update Protocol
+
+This KB must be re-synced whenever:
+- A task file is added, removed or renamed in `squads/squad-content/tasks/`
+- A new agent joins squad-content
+- A task primary changes owner
+
+The re-sync is run by `content-orqx` with co-sign from the affected primary/secondary agents.
+
+---
+
+## Change Log
+
+- 2026-04-12 — v1.0 authored as part of Story fw-v2.4 (squad-content v2.0 upgrade). 90 tasks mapped, 7 agents covered, 0 orphans, Arc over-load formally logged.

package/squads/squad-content/knowledge-base/video-audio-content-playbook.md

@@ -0,0 +1,218 @@
+# Video & Audio Content Playbook
+
+> Fonte: MS-008 Content Strategy Research (2026-04-07). Dados de plataformas verificados.
+
+---
+
+## 1. YouTube Strategy
+
+YouTube e o 2o maior mecanismo de busca do mundo. ~2.5-2.6 bilhoes de usuarios ativos mensais em 2025, ~2.85 bilhoes em 2026.
+
+**Estrategia de crescimento em fases:**
+
+```
+Fase 1 — Foundation (0-1K subscribers)
+├── Definir nicho especifico
+├── Publicar 2-3 videos/semana
+├── Focar em search content (how-tos, tutoriais)
+├── Titles e thumbnails otimizados para CTR
+└── Objetivo: encontrar o formato que funciona
+
+Fase 2 — Growth (1K-10K)
+├── Manter cadencia
+├── Expandir para browse/suggested content
+├── Series e playlists
+├── Community engagement (comentarios, community posts)
+└── Objetivo: crescimento sustentavel
+
+Fase 3 — Scale (10K-100K+)
+├── Mix de search + browse + subscriber content
+├── Colaboracoes com outros criadores
+├── Content diversification (Shorts, livestreams)
+├── Monetizacao (AdSense, sponsorships, products)
+└── Objetivo: autoridade no nicho
+```
+
+---
+
+## 2. Video SEO para YouTube
+
+| Fator | Otimizacao |
+|-------|-----------|
+| **Title** | Keyword no inicio, < 60 chars, ganchos de curiosidade |
+| **Description** | 200+ palavras, keyword nos primeiros 100 chars, timestamps, links |
+| **Tags** | 5-15 tags relevantes (keyword principal + variacoes + topico amplo) |
+| **Thumbnail** | Custom, alto contraste, face expressiva, texto curto |
+| **Chapters** | Timestamps no formato 0:00 na descricao (gera key moments no Google) |
+| **Cards & End Screens** | Link para videos relacionados (aumenta session time) |
+| **Closed Captions** | Upload de SRT (nao apenas auto-generated) |
+| **Filename** | keyword-no-filename.mp4 (antes do upload) |
+| **First 48h** | Periodo critico — impressoes iniciais determinam alcance |
+
+**Sinais de ranking YouTube:**
+
+| Sinal | Peso | Como Otimizar |
+|-------|------|---------------|
+| Watch Time | Muito Alto | Loops de retencao, pattern interrupts, manter ritmo |
+| CTR (Thumbnail + Title) | Alto | Thumbnail forte, titulo com curiosity gap |
+| Session Time | Alto | Conteudo que leva a mais videos, playlists |
+| Comments | Medio | CTA para comentar, perguntas no video |
+
+---
+
+## 3. Short-Form Video (Reels, TikTok, Shorts)
+
+**Dados de mercado (2026):**
+- TikTok: ~1.9 bilhoes de usuarios ativos mensais
+- YouTube Shorts: 200+ bilhoes de views diarias (2025), vs 70 bilhoes em 2024
+- Instagram Reels: maior formato de crescimento da plataforma
+
+**A regra dos 3 segundos:** 65% dos viewers decidem nos primeiros 3 segundos se continuam assistindo.
+
+**Tipos de Hook para Short-Form:**
+
+| Tipo de Hook | Exemplo |
+|-------------|---------|
+| Controversial statement | "Content marketing esta morto. Aqui esta o que funciona." |
+| Question | "Voce sabe por que 90% dos blogs nao geram leads?" |
+| Number/Stat | "Essa tecnica triplicou nosso trafego em 30 dias" |
+| Before/After | "Minha newsletter tinha 200 inscritos. Hoje tem 50.000." |
+| Tutorial promise | "Em 30 segundos voce vai aprender a escrever headlines 3x melhores" |
+| Pattern interrupt | Comeca com acao inesperada, corte rapido, som diferente |
+
+**Producao de short-form:**
+- Formato vertical (9:16), 1080x1920px
+- Legendas em tela (85% assiste sem som)
+- Cortes rapidos (2-3 segundos entre transicoes)
+- Texto overlay para pontos-chave
+- Musica trending (quando aplicavel ao contexto da marca)
+- Chamada final (follow, compartilha, comenta)
+
+---
+
+## 4. Tipos de Video Content
+
+| Tipo | Producao Necessaria | Uso Ideal |
+|------|---------------------|-----------|
+| **Talking Head** | Camera + mic + iluminacao | Opiniao, analise, storytelling |
+| **Screen Share** | Screen recording + voiceover | Tutoriais, demonstracoes |
+| **B-Roll Narrative** | Camera + B-roll + voiceover | Documentarios, case studies |
+| **Interview** | 2+ cameras + mics | Podcasts video, expert content |
+| **Animation** | Motion graphics software | Explainers, conceitos abstratos |
+| **Hybrid** | Mix de formatos | Maior engajamento, variedade visual |
+
+---
+
+## 5. Workflow de Producao de Video
+
+```
+Pre-Producao:
+├── Briefing / Script / Outline
+├── Shot list (B-roll necessario)
+├── Locacao / Setup (iluminacao, audio, camera)
+├── Teleprompter ou bullet points
+└── Thumbnail planejada
+
+Producao:
+├── Gravar intro/hook primeiro (energia maxima)
+├── Gravar corpo em blocos (facilita edicao)
+├── Gravar B-roll separadamente
+├── Gravar CTA/outro
+└── Verificar audio e enquadramento
+
+Pos-Producao:
+├── Rough cut (montar estrutura)
+├── Fine cut (cortar pausas, erros, tangentes)
+├── Color grading
+├── Audio mixing (nivelamento, musica, SFX)
+├── Motion graphics (lower thirds, texto)
+├── Thumbnail design
+├── Export em resolucoes necessarias
+└── Upload + otimizacao (title, desc, tags)
+```
+
+---
+
+## 6. Podcasting Strategy
+
+Podcast e o formato mais eficaz para construcao de autoridade profunda. Diferente de um blog post (5 minutos de leitura), um podcast ocupa 30-60 minutos da atencao do ouvinte.
+
+**Mercado global (2025-2026):**
+- ~584 milhoes de ouvintes globais em 2025, projetados para 619 milhoes em 2026
+- Mercado global: USD 30.7 bilhoes (2024), projetado para USD 131 bilhoes ate 2030 (CAGR 27%)
+- Brasil: 2o maior mercado de podcasts do mundo (apos EUA), com ~44% da populacao ouvindo semanalmente
+
+**Estrategia de podcast em 4 dimensoes:**
+
+```
+1. POSICIONAMENTO
+   ├── Nicho especifico (nao "marketing" — mas "content strategy para SaaS B2B")
+   ├── Formato (interview, solo, panel, narrative)
+   ├── Cadencia (semanal e o padrao — consistencia > frequencia)
+   ├── Duracao (30-60min para conversas, 15-20min para solo)
+   └── Tom e personalidade do host
+
+2. PRODUCAO
+   ├── Equipamento minimo: mic USB decente (Blue Yeti, Rode NT-USB Mini)
+   ├── Software de gravacao: Riverside.fm, Zencastr (remoto), Audacity (local)
+   ├── Edicao: Descript (edita audio como texto), Adobe Podcast (AI enhancement)
+   ├── Hosting: Spotify for Podcasters, Buzzsprout, Podbean, Transistor
+   └── Arte: Capa 3000x3000px, consistente com marca
+
+3. DISTRIBUICAO
+   ├── RSS feed → todos os diretorios automaticamente
+   ├── Spotify, Apple Podcasts, YouTube Music, Amazon Music
+   ├── YouTube (versao video do podcast = 2x audiencia)
+   ├── Social clips (cortes de 30-60s para Reels/TikTok)
+   └── Newsletter (show notes + link do episodio)
+   
+   NOTA: Google Podcasts foi descontinuado em 2024, migrado para YouTube Music.
+
+4. CRESCIMENTO
+   ├── Convidados com audiencia propria (cross-pollination)
+   ├── Guest appearances em outros podcasts
+   ├── SEO das show notes
+   ├── Social media promotion
+   └── Comunidade de ouvintes (Discord, Telegram)
+```
+
+---
+
+## 7. Monetizacao de Podcast
+
+| Modelo | Descricao | Quando Aplicar |
+|--------|-----------|---------------|
+| **Sponsorship** | Marcas pagam por mencao (pre/mid/post-roll) | 5.000+ downloads/episodio |
+| **Premium Content** | Episodios exclusivos para assinantes | Audiencia engajada |
+| **Afiliados** | Comissao por vendas via link/codigo | Desde o inicio |
+| **Produtos proprios** | Curso, consultoria, comunidade | Apos estabelecer autoridade |
+| **Doacoes** | Patreon, Apoia.se, Buy Me a Coffee | Comunidade fiel |
+| **Eventos** | Lives pagas, workshops, meetups | Audiencia local/engajada |
+
+---
+
+## 8. Show Notes SEO
+
+Show notes sao paginas de texto que acompanham cada episodio. Com otimizacao correta, geram trafego organico duradouro.
+
+**Componentes de show notes eficazes:**
+- Titulo com keyword primaria
+- Resumo do episodio (200-400 palavras)
+- Timestamps principais (chapters)
+- Transcricao completa ou parcial
+- Links para fontes mencionadas
+- Bio do convidado (com links)
+- CTAs (subscribe, newsletter, produto)
+- Schema markup (Podcast, Episode)
+
+---
+
+## Referências
+
+- YouTube Creator Academy — creatoracademy.youtube.com
+- Spotify for Podcasters — podcasters.spotify.com
+- Riverside.fm — producao de podcast remoto
+- Descript — edicao de audio/video
+- CMI — Video Content Strategy (relatorio anual)
+- Nieman Lab — Brazil podcast market
+- Podnews — Podcast industry news