sinapse-ai 9.4.0 → 9.5.0

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

@@ -0,0 +1,234 @@
+# 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
+> **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.
+
+---
+
+## 1. Why v2 Exists
+
+The v1 KB (`signal-detection-methods.md`) was written assuming a pre-Grok / pre-Apify-ubiquity landscape. Since then:
+
+- **X (Twitter) API v2** has become the dominant surface for public discourse, with tier changes that reshape what's scrapable.
+- **TikTok Research API** became available for commercial signal detection and is now the #1 cultural-signal source for sub-25 audiences.
+- **Apify actors** became the pragmatic alternative when APIs are closed — a rented actor marketplace for scraping any social surface.
+- **Grok on X** became a first-order summarizer of live discourse, shifting the signal-detection workflow.
+- **Substack** became a newsletter-first signal source for professional niches.
+- **Reddit API** re-opened for commercial use under new pricing.
+- **Google Trends + YouTube Data API v3** remain stable but are now cross-referenced against the above rather than primary.
+
+v1 still defines what a signal IS and the 7 signal types. v2 defines where signals LIVE in 2026 and how to score them.
+
+---
+
+## 2. Current-State Signal Source Catalog
+
+### 2.1 Tier A — First-party research APIs (highest trust)
+
+| Source | Access | Rate | Best for | Cost |
+|--------|--------|------|---------|------|
+| X API v2 (Basic/Pro/Enterprise) | OAuth 2.0, Basic tier ~$100/mo | ~10k posts/mo Basic | Real-time discourse, influencer signals, thread analysis, Grok summaries | Paid |
+| TikTok Research API | Academic/commercial app approval | Batch hashtag queries | Cultural signals, sub-25 behavior, meme velocity, trend lifecycle | Free with approval |
+| YouTube Data API v3 | Google Cloud key | 10k units/day free | Long-form trend signals, creator signals, search intent behind video queries | Free tier + paid |
+| Reddit API (official) | OAuth 2.0, commercial tier | Paid tiers for commercial | Niche community signals, question mining, "authentic voice" samples | Paid for commercial |
+| Google Trends API (pytrends + official) | Public, rate-limited | Rolling | Search intent velocity, regional variation, seasonality | Free |
+
+### 2.2 Tier B — Scraping / Actor-based sources
+
+| Source | Access | Best for | Legal/ToS note |
+|--------|--------|---------|----------------|
+| Apify actors (Instagram, TikTok, LinkedIn, X, etc.) | Apify platform pay-per-run | Whatever is not open via official API | Respect robots.txt + ToS, document legal basis per actor |
+| Substack RSS feeds | Public RSS | Professional niche signals, newsletter thesis drift | Public RSS is safe |
+| Newsletter aggregators (Feedly, Inoreader) | API keys | Curated professional signals by editor | OK |
+| Podcast RSS + transcription (Whisper) | Public RSS + local Whisper | Long-form thesis signals before they hit text | Respect IP/quotation rules |
+
+### 2.3 Tier C — Curated human-intelligence
+
+| Source | Why | Cadence |
+|--------|-----|---------|
+| Exploding Topics | Trend pre-emergence detection | Weekly digest |
+| SparkToro | Audience intelligence + zero-click research | On demand |
+| BuzzSumo | Evergreen scoring + viral performance | On demand |
+| Semrush Trends | SEO-backed topic signals | Rolling |
+| Parse.ly Currents | Publisher-side trend intelligence | Daily |
+| Stacked Marketer / Morning Brew / The Hustle / Superpath | Human-curated daily scan | Daily |
+
+### 2.4 Tier D — Proprietary client signals (highest leverage)
+
+| Source | Why it matters |
+|--------|---------------|
+| Client DMs, comments, reviews, support tickets | Authentic audience voice — highest-leverage signal, hardest to find |
+| Client analytics (Parse.ly, GA4, native platform analytics) | Performance signals closing the loop back to retrofeed |
+| Sales team transcripts (Gong, Fireflies) | What the market is saying with buying intent |
+| Customer interview transcripts (Whisper) | Pain language, vocabulary, objections |
+
+**Rule of thumb:** Tier D signals > Tier A > Tier B > Tier C for relevance. Tier C and A are broader-coverage; Tier D is narrower-but-hotter.
+
+---
+
+## 3. Signal Classification Taxonomy
+
+Every detected signal MUST be classified into exactly one of these 5 categories. Classification determines routing to Phase 2 (AI Draft) and the editorial pillar mapping.
+
+### 3.1 Opportunity Window
+
+**Definition:** A short-lived condition where content on a specific topic will over-perform because attention is concentrated.
+**Velocity:** Hours to 7 days.
+**Example:** Apple releases a new dev tool at WWDC — window to publish "what this means for SaaS founders" is 48-72h before commodity hot-takes flood the channel.
+**Routing:** Phase 1 → Phase 2 immediately, high urgency, human-edit fast-track.
+**Failure mode:** Late-to-the-window = commodity content.
+
+### 3.2 Trend Seed
+
+**Definition:** Early sign of a topic gaining velocity before it becomes mainstream. Detected pre-inflection.
+**Velocity:** Weeks to months.
+**Example:** A term starts appearing in 3+ unrelated niche newsletters over 2 weeks. Not yet on Google Trends.
+**Routing:** Phase 1 → editorial calendar insertion, build a pillar-aligned series.
+**Failure mode:** Calling a trend too early or forcing a seed that won't grow.
+
+### 3.3 Crisis Alert
+
+**Definition:** A brand-relevant event that forces a response — competitor misstep, industry controversy, client-adjacent scandal, regulatory change.
+**Velocity:** Immediate (hours).
+**Example:** A major competitor gets caught in a data breach — opportunity for a thoughtful "here is how we think about data stewardship" piece.
+**Routing:** Phase 1 → escalate to client immediately, Phase 2 requires human-heavy review (high reputational stakes).
+**Failure mode:** Opportunistic copy that reads as vulture-like; miss the window of relevance.
+
+### 3.4 Category Shift
+
+**Definition:** A slow but durable change in how the category thinks, talks or operates. Signals arrive from multiple unrelated sources over time.
+**Velocity:** Months to quarters.
+**Example:** The shift from "content marketing" to "audience-first content" in 2018-2021. You can see it in retrospect; the leverage is seeing it 6 months before the category does.
+**Routing:** Phase 1 → manifesto piece + editorial pillar reshape, high authority play.
+**Failure mode:** Chasing every language shift as if it were a category shift.
+
+### 3.5 Competitor Move
+
+**Definition:** A direct, attributable action by a known competitor — launch, campaign, messaging shift, hiring pattern, product change.
+**Velocity:** Days to weeks.
+**Example:** Competitor launches a new tier; opportunity to reframe your own positioning.
+**Routing:** Phase 1 → analyst pass (`benchmark-against-competitors`) → Phase 2 strategic response content.
+**Failure mode:** Obsessively responding to competitors instead of leading the category.
+
+---
+
+## 4. Signal-to-Pillar Routing Rules
+
+Every signal must be routed to an editorial pillar before it enters Phase 2. Unrouted signals are archived.
+
+### 4.1 Routing Algorithm
+
+```
+1. Classify signal into one of 5 categories (§3)
+2. Match signal to existing editorial pillars via semantic overlap
+3. If match → route to pillar, schedule in Phase 2 queue
+4. If no match → check if the signal is a Category Shift (rare but possible)
+   - YES → escalate to editorial-strategist for pillar review
+   - NO → archive with "no pillar fit" tag
+5. If match spans multiple pillars → assign primary pillar + cross-reference secondary
+```
+
+### 4.2 Routing Priority Matrix
+
+| Signal Category | Priority | Route Directly To |
+|----------------|----------|-------------------|
+| Crisis Alert | P0 | content-orqx → editorial-strategist (escalation) |
+| Opportunity Window | P1 | Phase 2 fast-track, content-engineer |
+| Competitor Move | P2 | content-analyst benchmark, then content-engineer |
+| Trend Seed | P3 | editorial-strategist for calendar insertion |
+| Category Shift | P3 | editorial-strategist for pillar reshape consideration |
+
+---
+
+## 5. Signal Quality Scoring
+
+Every signal, before entering Phase 2, is scored 1-5 on 5 dimensions. A signal must score ≥ 3.0 average to enter Phase 2.
+
+| Dimension | 1 | 5 |
+|-----------|---|---|
+| **Relevance** to pillar/client | Unrelated | Perfect pillar fit |
+| **Novelty** vs prior content | Covered recently | Fresh angle |
+| **Evidence** backing the signal | 1 weak source | 3+ independent sources |
+| **Actionability** for target audience | No clear reader action | Clear reader takeaway |
+| **Window** still open | Closed/saturated | Open and ahead of curve |
+
+Final score = average of 5 dimensions. Below 3.0 → archive. 3.0-4.0 → Phase 2 standard. 4.0-5.0 → Phase 2 priority + optional cross-platform batch.
+
+---
+
+## 6. Source Monitoring Cadence
+
+| Tier | Source | Cadence |
+|------|--------|---------|
+| A | X API v2 | Continuous (webhooks/streams where possible) |
+| A | TikTok Research API | Daily batch query per pillar |
+| A | YouTube Data API | Daily batch |
+| A | Reddit API | Twice daily |
+| A | Google Trends | Twice daily |
+| B | Apify actors | Daily (rotating by cost) |
+| B | Substack RSS | Continuous |
+| C | Exploding Topics / SparkToro / BuzzSumo | Weekly |
+| C | Newsletters | Daily at fixed time |
+| D | Client DMs / analytics | Continuous |
+| D | Sales transcripts | Weekly batch |
+
+---
+
+## 7. Anti-Patterns (v2 additions over v1)
+
+- **API-only monitoring** — missing Tier D (client-proprietary) signals is the most expensive blind spot.
+- **Grok as sole summarizer** — powerful but opinionated; cross-reference with raw X posts.
+- **Scraping without legal basis** — Tier B Apify usage must document basis per actor.
+- **Treating Crisis Alerts as Opportunity Windows** — speed without care damages brand.
+- **Category Shift false positives** — most language shifts are not category shifts; require multi-source, multi-month evidence.
+- **Signals without routing** — unrouted signals clutter the pipeline and never become content.
+- **Ignoring Tier D in favor of Tier A** — public-web signals are the same ones everyone else sees.
+
+---
+
+## 8. Handoff to Phase 2 (AI Draft)
+
+When a signal passes quality scoring and routing, the hand-off package to Phase 2 contains:
+
+```
+signal:
+  id: sig-{yyyymmdd}-{n}
+  category: opportunity_window | trend_seed | crisis_alert | category_shift | competitor_move
+  source_tier: A | B | C | D
+  source_name: e.g., "X API v2"
+  evidence:
+    - url: ...
+      excerpt: ...
+    - url: ...
+      excerpt: ...
+  pillar_primary: ...
+  pillar_secondary: [...]
+  quality_score: 4.2
+  window_open_until: 2026-04-15T18:00Z
+  suggested_thesis: "..."
+  suggested_format: ["carousel", "thread"]
+```
+
+This is the structured input that `content-engineer` (Arc) consumes at Phase 2 of `ai-native-content-loop.md`.
+
+---
+
+## 9. Relationship to v1 KB
+
+| Topic | v1 (signal-detection-methods.md) | v2 (this KB) |
+|-------|----------------------------------|--------------|
+| What is a signal | DEFINITIVE | Referenced |
+| 7 signal types | DEFINITIVE | Referenced |
+| Source catalog | Stale (2026 update) | **DEFINITIVE** |
+| Classification taxonomy | Not covered | **DEFINITIVE** |
+| Routing rules | Not covered | **DEFINITIVE** |
+| Quality scoring | Not covered | **DEFINITIVE** |
+| Handoff format | Not covered | **DEFINITIVE** |
+
+---
+
+## Change Log
+
+- 2026-04-12 — v1.0 authored as part of Story fw-v2.4 (squad-content v2.0 upgrade). Additive to v1 signal-detection-methods.md — v1 is NOT modified.

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.