@jaimevalasek/aioson 1.8.0 → 1.9.1

package/template/.aioson/tasks/squad-task-decompose.md

@@ -1,66 +1,66 @@
-# Task: Squad Task Decomposition
-
-> Guia de decomposição de executores em tasks granulares.
-
-## Quando usar
-- Durante `@squad create`, ao avaliar cada executor
-- `@squad extend` quando o usuário pede task decomposition retroativa
-
-## Formato de um task file
-
-Salvar em `.aioson/squads/{squad-slug}/agents/{executor-slug}/tasks/{task-slug}.md`:
-
-```markdown
-# Task: {task-name}
-
-> Order: {1, 2, 3...}
-> Executor: @{executor-slug}
-> Input: {what this task receives}
-> Output: {what this task produces}
-
-## Process
-1. {Step 1 — concrete action}
-2. {Step 2 — concrete action}
-3. {Step 3 — concrete action}
-
-## Output Format
-{Schema or description of expected output}
-
-## Output Example
-{15+ lines of realistic output example}
-
-## Quality Criteria
-1. {Measurable criterion}
-2. {Measurable criterion}
-3. {Measurable criterion}
-
-## Veto Conditions
-1. {Hard block — output CANNOT have this}
-2. {Hard block — output CANNOT have this}
-```
-
-## Árvore de decisão
-
-```
-EXECUTOR
-  ├── Faz UMA coisa bem? (reviewer, validator, formatter)
-  │   └── SEM tasks — o agent file é suficiente
-  │
-  ├── Tem processo multi-step repetível?
-  │   ├── 2 steps → provavelmente sem tasks (mantenha simples)
-  │   ├── 3+ steps com outputs distintos → SIM, decompor em tasks
-  │   └── 3+ steps internos → SEM tasks (steps no agent file)
-  │
-  ├── As tasks serão reutilizadas?
-  │   └── SIM → decompor (reusabilidade)
-  │
-  └── Qualidade é crítica e cada step precisa de seus critérios?
-      └── SIM → decompor (controle granular de qualidade)
-```
-
-## Regras
-- Manter o agent file focado na identidade (missão, foco, restrições)
-- Mover detalhes de processo para task files
-- Cada task deve ser independentemente avaliável
-- Tasks executam sequencialmente — output da task N é input da task N+1
-- Adicionar quality criteria por task, não só por executor
+# Task: Squad Task Decomposition
+
+> Guia de decomposição de executores em tasks granulares.
+
+## Quando usar
+- Durante `@squad create`, ao avaliar cada executor
+- `@squad extend` quando o usuário pede task decomposition retroativa
+
+## Formato de um task file
+
+Salvar em `.aioson/squads/{squad-slug}/agents/{executor-slug}/tasks/{task-slug}.md`:
+
+```markdown
+# Task: {task-name}
+
+> Order: {1, 2, 3...}
+> Executor: @{executor-slug}
+> Input: {what this task receives}
+> Output: {what this task produces}
+
+## Process
+1. {Step 1 — concrete action}
+2. {Step 2 — concrete action}
+3. {Step 3 — concrete action}
+
+## Output Format
+{Schema or description of expected output}
+
+## Output Example
+{15+ lines of realistic output example}
+
+## Quality Criteria
+1. {Measurable criterion}
+2. {Measurable criterion}
+3. {Measurable criterion}
+
+## Veto Conditions
+1. {Hard block — output CANNOT have this}
+2. {Hard block — output CANNOT have this}
+```
+
+## Árvore de decisão
+
+```
+EXECUTOR
+  ├── Faz UMA coisa bem? (reviewer, validator, formatter)
+  │   └── SEM tasks — o agent file é suficiente
+  │
+  ├── Tem processo multi-step repetível?
+  │   ├── 2 steps → provavelmente sem tasks (mantenha simples)
+  │   ├── 3+ steps com outputs distintos → SIM, decompor em tasks
+  │   └── 3+ steps internos → SEM tasks (steps no agent file)
+  │
+  ├── As tasks serão reutilizadas?
+  │   └── SIM → decompor (reusabilidade)
+  │
+  └── Qualidade é crítica e cada step precisa de seus critérios?
+      └── SIM → decompor (controle granular de qualidade)
+```
+
+## Regras
+- Manter o agent file focado na identidade (missão, foco, restrições)
+- Mover detalhes de processo para task files
+- Cada task deve ser independentemente avaliável
+- Tasks executam sequencialmente — output da task N é input da task N+1
+- Adicionar quality criteria por task, não só por executor

package/template/.aioson/tasks/squad-validate.md

@@ -1,58 +1,58 @@
-# Task: Squad Validate
-
-> Fase de validação do lifecycle. Verifica consistência do pacote.
-
-## Quando usar
-- `@squad validate <slug>` — invocação direta
-- Automaticamente após `@squad create`
-- Quando o CLI `aioson squad:validate <slug>` é executado
-
-## Entrada
-- slug do squad (deve existir em `.aioson/squads/<slug>/`)
-
-## Processo
-
-### Camada 1 — Validação de schema
-1. Leia `.aioson/squads/<slug>/squad.manifest.json`
-2. Valide contra `.aioson/schemas/squad-manifest.schema.json`
-3. Campos obrigatórios: schemaVersion, slug, name, mode, mission, goal
-4. Se falhar: ERRO com campo faltante e sugestão
-
-### Camada 2 — Validação estrutural
-Verifique que existem:
-- `.aioson/squads/<slug>/squad.manifest.json` (obrigatório)
-- `.aioson/squads/<slug>/agents/agents.md` (obrigatório)
-- `.aioson/squads/<slug>/agents/orquestrador.md` (obrigatório)
-- Para cada executor em manifest.executors: o arquivo referenciado existe
-- Diretórios: `output/<slug>/`, `aioson-logs/<slug>/`
-
-### Camada 3 — Validação semântica (básica nesta fase, aprofundada na Fase 2)
-- Slug do manifesto bate com o nome do diretório
-- Executores no manifesto têm arquivo correspondente
-- Não há executores duplicados
-
-### Relatório
-Classifique cada check como:
-- ✅ PASS
-- ⚠️ WARNING (não bloqueia, mas recomenda correção)
-- ❌ ERROR (bloqueia — squad inválido)
-
-Formato de output:
-```
-═══ Squad Validation: <slug> ═══
-
-Schema:     ✅ PASS
-Structure:  ✅ PASS (7/7 files found)
-Semantics:  ⚠️ 1 warning
-  - executor "analyst" has no skills declared
-
-Result: VALID (1 warning)
-```
-
-## Saída
-- Relatório de validação (console)
-- Status: VALID | VALID_WITH_WARNINGS | INVALID
-
-## Regras
-- NÃO corrija problemas automaticamente — apenas reporte
-- SUGIRA o comando de correção quando possível (ex: "run @squad extend to add skills")
+# Task: Squad Validate
+
+> Fase de validação do lifecycle. Verifica consistência do pacote.
+
+## Quando usar
+- `@squad validate <slug>` — invocação direta
+- Automaticamente após `@squad create`
+- Quando o CLI `aioson squad:validate <slug>` é executado
+
+## Entrada
+- slug do squad (deve existir em `.aioson/squads/<slug>/`)
+
+## Processo
+
+### Camada 1 — Validação de schema
+1. Leia `.aioson/squads/<slug>/squad.manifest.json`
+2. Valide contra `.aioson/schemas/squad-manifest.schema.json`
+3. Campos obrigatórios: schemaVersion, slug, name, mode, mission, goal
+4. Se falhar: ERRO com campo faltante e sugestão
+
+### Camada 2 — Validação estrutural
+Verifique que existem:
+- `.aioson/squads/<slug>/squad.manifest.json` (obrigatório)
+- `.aioson/squads/<slug>/agents/agents.md` (obrigatório)
+- `.aioson/squads/<slug>/agents/orquestrador.md` (obrigatório)
+- Para cada executor em manifest.executors: o arquivo referenciado existe
+- Diretórios: `output/<slug>/`, `aioson-logs/<slug>/`
+
+### Camada 3 — Validação semântica (básica nesta fase, aprofundada na Fase 2)
+- Slug do manifesto bate com o nome do diretório
+- Executores no manifesto têm arquivo correspondente
+- Não há executores duplicados
+
+### Relatório
+Classifique cada check como:
+- ✅ PASS
+- ⚠️ WARNING (não bloqueia, mas recomenda correção)
+- ❌ ERROR (bloqueia — squad inválido)
+
+Formato de output:
+```
+═══ Squad Validation: <slug> ═══
+
+Schema:     ✅ PASS
+Structure:  ✅ PASS (7/7 files found)
+Semantics:  ⚠️ 1 warning
+  - executor "analyst" has no skills declared
+
+Result: VALID (1 warning)
+```
+
+## Saída
+- Relatório de validação (console)
+- Status: VALID | VALID_WITH_WARNINGS | INVALID
+
+## Regras
+- NÃO corrija problemas automaticamente — apenas reporte
+- SUGIRA o comando de correção quando possível (ex: "run @squad extend to add skills")

package/template/.aioson/templates/reflect-prompts/current-state.md

@@ -0,0 +1,36 @@
+# Reflect prompt — `bootstrap/current-state.md`
+
+You just finished a session that the memory engine marked as **relevant**. Refresh `bootstrap/current-state.md` so it reflects the project as it is *now*, not as it was at the last reflection.
+
+## What to do
+1. Read the current content of `.aioson/context/bootstrap/current-state.md` (it is also in `current_bootstrap_snapshot["current-state.md"]` of the manifest).
+2. Read `diff_summary`, `changed_files`, and `heuristic_reasons` from the manifest.
+3. Update the file in place:
+   - **Add** new capabilities or modules the session shipped.
+   - **Remove** entries that are no longer true (removed features, retired modules).
+   - **Keep** untouched anything outside the changed scope.
+   - **Preserve** the YAML frontmatter; only update the `generated_at` field to the current ISO 8601 timestamp.
+4. Be terse. One line per capability. No marketing language.
+5. Do not invent. If a fact is not present in the diff or already in the file, leave it alone.
+
+## What NOT to do
+- Do not edit any file outside `validation_rules.allowed_paths`.
+- Do not rewrite the entire file when a small edit suffices.
+- Do not remove the frontmatter or change `name`/`scope` fields.
+
+## How to commit
+Emit one JSON object to stdin of `aioson memory:reflect-commit`:
+
+```json
+{
+  "files": {
+    ".aioson/context/bootstrap/current-state.md": "<new full content>"
+  }
+}
+```
+
+Or write the JSON to a file and run:
+
+```
+aioson memory:reflect-commit . --agent=<your-agent> --output=<path-to-json>
+```

package/template/.aioson/templates/reflect-prompts/how-it-works.md

@@ -0,0 +1,23 @@
+# Reflect prompt — `bootstrap/how-it-works.md`
+
+The session touched architecture, routes, models, or migrations. Refresh `bootstrap/how-it-works.md` so it stays faithful to the new shape of the system.
+
+## What to do
+1. Read the current content of `.aioson/context/bootstrap/how-it-works.md` (also in `current_bootstrap_snapshot["how-it-works.md"]`).
+2. Inspect `changed_files` and the diff. Focus on:
+   - new modules / handlers / controllers
+   - new tables / models / migrations
+   - data-flow changes implied by them
+3. Update the file:
+   - **Add** the new architectural piece in the appropriate section.
+   - **Remove** entries that were superseded by the refactor.
+   - **Preserve** frontmatter; bump `generated_at`.
+4. Keep the writing concrete and short. Each line should be verifiable against code.
+
+## What NOT to do
+- Do not paraphrase the diff line by line. Summarize the *shape*, not the changes.
+- Do not edit files outside `validation_rules.allowed_paths`.
+- Do not drift into product talk — that belongs in `what-it-does.md`.
+
+## How to commit
+Same protocol as the other reflect prompts: emit `{ "files": { ... } }` to `aioson memory:reflect-commit`.

package/template/.aioson/templates/reflect-prompts/what-it-does.md

@@ -0,0 +1,21 @@
+# Reflect prompt — `bootstrap/what-it-does.md`
+
+The session touched product contracts (PRDs, features.md, requirements). Refresh `bootstrap/what-it-does.md` so the list of features and business rules is current.
+
+## What to do
+1. Read the current content of `.aioson/context/bootstrap/what-it-does.md` (also in `current_bootstrap_snapshot["what-it-does.md"]`).
+2. Inspect `changed_files` for `prd-*.md`, `features.md`, `requirements-*.md`.
+3. Update the file:
+   - **Add** newly accepted features and business rules.
+   - **Remove** items now marked `done` and superseded, or features dropped from scope.
+   - **Reword** only when a rule's meaning materially changed.
+   - **Preserve** frontmatter; bump `generated_at`.
+4. Keep entries action-oriented and verifiable. One bullet per feature.
+
+## What NOT to do
+- Do not mix in implementation details (those belong in `how-it-works.md`).
+- Do not edit files outside `validation_rules.allowed_paths`.
+- Do not invent features that are not in the diff or already in the file.
+
+## How to commit
+Same protocol as the other reflect prompts: emit `{ "files": { ... } }` to `aioson memory:reflect-commit`.

package/template/.aioson/templates/squads/content-basic/template.json

@@ -1,21 +1,21 @@
-{
-  "slug": "content-basic",
-  "name": "Content Basic",
-  "description": "Squad genérico de conteúdo: artigos, scripts, copy, estratégia",
-  "mode": "content",
-  "suggestedExecutors": [
-    { "slug": "writer", "role": "Creates written content, articles, scripts" },
-    { "slug": "strategist", "role": "Defines content strategy, angles, positioning" },
-    { "slug": "editor", "role": "Reviews, improves clarity, fact-checks" }
-  ],
-  "defaultContentBlueprint": {
-    "slug": "content-piece",
-    "contentType": "article",
-    "layoutType": "document",
-    "sections": [
-      { "key": "main-content", "label": "Content", "blockTypes": ["rich-text"] },
-      { "key": "summary", "label": "Summary", "blockTypes": ["rich-text"] },
-      { "key": "tags", "label": "Tags", "blockTypes": ["tags"] }
-    ]
-  }
-}
+{
+  "slug": "content-basic",
+  "name": "Content Basic",
+  "description": "Squad genérico de conteúdo: artigos, scripts, copy, estratégia",
+  "mode": "content",
+  "suggestedExecutors": [
+    { "slug": "writer", "role": "Creates written content, articles, scripts" },
+    { "slug": "strategist", "role": "Defines content strategy, angles, positioning" },
+    { "slug": "editor", "role": "Reviews, improves clarity, fact-checks" }
+  ],
+  "defaultContentBlueprint": {
+    "slug": "content-piece",
+    "contentType": "article",
+    "layoutType": "document",
+    "sections": [
+      { "key": "main-content", "label": "Content", "blockTypes": ["rich-text"] },
+      { "key": "summary", "label": "Summary", "blockTypes": ["rich-text"] },
+      { "key": "tags", "label": "Tags", "blockTypes": ["tags"] }
+    ]
+  }
+}

package/template/.aioson/templates/squads/digital-marketing-agency/template.json

@@ -1,96 +1,96 @@
-{
-  "slug": "digital-marketing-agency",
-  "name": "Digital Marketing Agency",
-  "description": "Full-stack digital marketing squad: strategy, copy, landing pages, traffic, content, performance — 8 specialized roles for end-to-end campaign execution.",
-  "mode": "mixed",
-  "uiCapability": {
-    "mode": "skills",
-    "skills": ["landing-page-forge", "ui-ux-modern"]
-  },
-  "suggestedExecutors": [
-    {
-      "slug": "estrategista",
-      "role": "Marketing strategist — defines campaign goals, funnel architecture, audience, and assigns tasks to specialists",
-      "type": "agent",
-      "modelTier": "powerful",
-      "behavioralProfile": "dominant-influential"
-    },
-    {
-      "slug": "copywriter",
-      "role": "Writes all copy — headlines, body text, CTAs, email sequences, ad copy. Copy exists before any design.",
-      "type": "assistant",
-      "modelTier": "powerful",
-      "behavioralProfile": "influential-expressive"
-    },
-    {
-      "slug": "page-builder",
-      "role": "Builds landing pages, sales pages, and event pages — full production stack including animations, SEO/LLMO, tracking, and performance.",
-      "type": "agent",
-      "modelTier": "powerful",
-      "behavioralProfile": "compliant-dominant",
-      "skills": ["landing-page-forge", "ui-ux-modern"]
-    },
-    {
-      "slug": "traffic-manager",
-      "role": "Manages paid traffic — Meta Ads, Google Ads. Configures Pixel, UTMs, audiences, campaign structure.",
-      "type": "assistant",
-      "modelTier": "powerful",
-      "behavioralProfile": "compliant-analytical"
-    },
-    {
-      "slug": "seo-llmo",
-      "role": "Handles organic discoverability — SEO strategy, on-page optimization, LLMO (LLM.txt, structured data, AI search optimization).",
-      "type": "assistant",
-      "modelTier": "balanced",
-      "behavioralProfile": "compliant-analytical"
-    },
-    {
-      "slug": "content-creator",
-      "role": "Creates organic content — social posts, newsletters, blog articles, video scripts aligned with campaign goals.",
-      "type": "assistant",
-      "modelTier": "powerful",
-      "behavioralProfile": "influential-steady"
-    },
-    {
-      "slug": "performance-analyst",
-      "role": "Analyzes metrics — conversion rates, LCP/CLS, PageSpeed, funnel drop-offs, A/B test results. Reports and recommends optimizations.",
-      "type": "assistant",
-      "modelTier": "balanced",
-      "behavioralProfile": "compliant-analytical"
-    },
-    {
-      "slug": "orquestrador",
-      "role": "Coordinates the agency squad — routes tasks, synthesizes outputs, ensures copy exists before design, tracking before launch.",
-      "type": "agent",
-      "modelTier": "powerful",
-      "behavioralProfile": "dominant-influential"
-    }
-  ],
-  "defaultContentBlueprint": {
-    "slug": "campaign-package",
-    "contentType": "marketing-campaign",
-    "layoutType": "tabs",
-    "sections": [
-      { "key": "strategy", "label": "Strategy", "blockTypes": ["rich-text"] },
-      { "key": "copy", "label": "Copy", "blockTypes": ["rich-text", "copy-block"] },
-      { "key": "page-spec", "label": "Page Spec", "blockTypes": ["rich-text"] },
-      { "key": "tracking", "label": "Tracking Setup", "blockTypes": ["rich-text", "copy-block"] },
-      { "key": "seo-llmo", "label": "SEO/LLMO", "blockTypes": ["bullet-list", "copy-block"] },
-      { "key": "performance", "label": "Performance Report", "blockTypes": ["rich-text", "bullet-list"] }
-    ]
-  },
-  "productionGates": [
-    {
-      "gate": "copy-before-design",
-      "rule": "Copy must be approved by @copywriter before @page-builder starts layout work"
-    },
-    {
-      "gate": "tracking-before-launch",
-      "rule": "Pixel, GTM, and UTM capture must be verified by @traffic-manager before any paid traffic is sent"
-    },
-    {
-      "gate": "performance-before-launch",
-      "rule": "PageSpeed mobile ≥ 90 and LCP < 2.5s must be verified before launch"
-    }
-  ]
-}
+{
+  "slug": "digital-marketing-agency",
+  "name": "Digital Marketing Agency",
+  "description": "Full-stack digital marketing squad: strategy, copy, landing pages, traffic, content, performance — 8 specialized roles for end-to-end campaign execution.",
+  "mode": "mixed",
+  "uiCapability": {
+    "mode": "skills",
+    "skills": ["landing-page-forge", "ui-ux-modern"]
+  },
+  "suggestedExecutors": [
+    {
+      "slug": "estrategista",
+      "role": "Marketing strategist — defines campaign goals, funnel architecture, audience, and assigns tasks to specialists",
+      "type": "agent",
+      "modelTier": "powerful",
+      "behavioralProfile": "dominant-influential"
+    },
+    {
+      "slug": "copywriter",
+      "role": "Writes all copy — headlines, body text, CTAs, email sequences, ad copy. Copy exists before any design.",
+      "type": "assistant",
+      "modelTier": "powerful",
+      "behavioralProfile": "influential-expressive"
+    },
+    {
+      "slug": "page-builder",
+      "role": "Builds landing pages, sales pages, and event pages — full production stack including animations, SEO/LLMO, tracking, and performance.",
+      "type": "agent",
+      "modelTier": "powerful",
+      "behavioralProfile": "compliant-dominant",
+      "skills": ["landing-page-forge", "ui-ux-modern"]
+    },
+    {
+      "slug": "traffic-manager",
+      "role": "Manages paid traffic — Meta Ads, Google Ads. Configures Pixel, UTMs, audiences, campaign structure.",
+      "type": "assistant",
+      "modelTier": "powerful",
+      "behavioralProfile": "compliant-analytical"
+    },
+    {
+      "slug": "seo-llmo",
+      "role": "Handles organic discoverability — SEO strategy, on-page optimization, LLMO (LLM.txt, structured data, AI search optimization).",
+      "type": "assistant",
+      "modelTier": "balanced",
+      "behavioralProfile": "compliant-analytical"
+    },
+    {
+      "slug": "content-creator",
+      "role": "Creates organic content — social posts, newsletters, blog articles, video scripts aligned with campaign goals.",
+      "type": "assistant",
+      "modelTier": "powerful",
+      "behavioralProfile": "influential-steady"
+    },
+    {
+      "slug": "performance-analyst",
+      "role": "Analyzes metrics — conversion rates, LCP/CLS, PageSpeed, funnel drop-offs, A/B test results. Reports and recommends optimizations.",
+      "type": "assistant",
+      "modelTier": "balanced",
+      "behavioralProfile": "compliant-analytical"
+    },
+    {
+      "slug": "orquestrador",
+      "role": "Coordinates the agency squad — routes tasks, synthesizes outputs, ensures copy exists before design, tracking before launch.",
+      "type": "agent",
+      "modelTier": "powerful",
+      "behavioralProfile": "dominant-influential"
+    }
+  ],
+  "defaultContentBlueprint": {
+    "slug": "campaign-package",
+    "contentType": "marketing-campaign",
+    "layoutType": "tabs",
+    "sections": [
+      { "key": "strategy", "label": "Strategy", "blockTypes": ["rich-text"] },
+      { "key": "copy", "label": "Copy", "blockTypes": ["rich-text", "copy-block"] },
+      { "key": "page-spec", "label": "Page Spec", "blockTypes": ["rich-text"] },
+      { "key": "tracking", "label": "Tracking Setup", "blockTypes": ["rich-text", "copy-block"] },
+      { "key": "seo-llmo", "label": "SEO/LLMO", "blockTypes": ["bullet-list", "copy-block"] },
+      { "key": "performance", "label": "Performance Report", "blockTypes": ["rich-text", "bullet-list"] }
+    ]
+  },
+  "productionGates": [
+    {
+      "gate": "copy-before-design",
+      "rule": "Copy must be approved by @copywriter before @page-builder starts layout work"
+    },
+    {
+      "gate": "tracking-before-launch",
+      "rule": "Pixel, GTM, and UTM capture must be verified by @traffic-manager before any paid traffic is sent"
+    },
+    {
+      "gate": "performance-before-launch",
+      "rule": "PageSpeed mobile ≥ 90 and LCP < 2.5s must be verified before launch"
+    }
+  ]
+}

package/template/.aioson/templates/squads/media-channel/template.json

@@ -1,24 +1,24 @@
-{
-  "slug": "media-channel",
-  "name": "Media Channel",
-  "description": "Squad para canal de mídia: YouTube, podcast, newsletter, social",
-  "mode": "content",
-  "suggestedExecutors": [
-    { "slug": "scriptwriter", "role": "Writes scripts, outlines, narratives" },
-    { "slug": "title-generator", "role": "Creates titles, hooks, angles" },
-    { "slug": "copywriter", "role": "Writes descriptions, CTAs, social copy" },
-    { "slug": "trend-analyst", "role": "Researches trends, competitors, opportunities" }
-  ],
-  "defaultContentBlueprint": {
-    "slug": "media-package",
-    "contentType": "media-package",
-    "layoutType": "tabs",
-    "sections": [
-      { "key": "script", "label": "Script/Outline", "blockTypes": ["rich-text"] },
-      { "key": "titles", "label": "Title Options", "blockTypes": ["bullet-list"] },
-      { "key": "description", "label": "Description", "blockTypes": ["rich-text"] },
-      { "key": "tags", "label": "Tags & Keywords", "blockTypes": ["tags"] },
-      { "key": "thumbnail", "label": "Thumbnail Brief", "blockTypes": ["rich-text"] }
-    ]
-  }
-}
+{
+  "slug": "media-channel",
+  "name": "Media Channel",
+  "description": "Squad para canal de mídia: YouTube, podcast, newsletter, social",
+  "mode": "content",
+  "suggestedExecutors": [
+    { "slug": "scriptwriter", "role": "Writes scripts, outlines, narratives" },
+    { "slug": "title-generator", "role": "Creates titles, hooks, angles" },
+    { "slug": "copywriter", "role": "Writes descriptions, CTAs, social copy" },
+    { "slug": "trend-analyst", "role": "Researches trends, competitors, opportunities" }
+  ],
+  "defaultContentBlueprint": {
+    "slug": "media-package",
+    "contentType": "media-package",
+    "layoutType": "tabs",
+    "sections": [
+      { "key": "script", "label": "Script/Outline", "blockTypes": ["rich-text"] },
+      { "key": "titles", "label": "Title Options", "blockTypes": ["bullet-list"] },
+      { "key": "description", "label": "Description", "blockTypes": ["rich-text"] },
+      { "key": "tags", "label": "Tags & Keywords", "blockTypes": ["tags"] },
+      { "key": "thumbnail", "label": "Thumbnail Brief", "blockTypes": ["rich-text"] }
+    ]
+  }
+}