CB-003 — Scout Signal Intake Pipeline
Purpose
Establish a governed refinement layer between raw external signal and operational Atlantis decisions. Raw intelligence — news, repos, social chatter, research papers — must pass through a structured review chain before it can influence Council decisions, the weekly Chronicle, or any automated routing.
The Pipeline
| Stage | Owner | Function |
|---|---|---|
| 1 | Scout | Signal capture + source tagging |
| 2 | Cooper | Structure + clean summary |
| 3 | Lyra | Verification + context |
| 4 | Jimmy | Governance / risk / privacy flags |
| 5 | Ozzy | Architecture fit check |
| 6 | Mercy | Executive briefing + recommended action |
| 7 | Nova | Routes — only if approved through Stage 6 |
Source Confidence Tiers
| Tier | Sources |
|---|---|
| HIGH | GitHub, ArXiv, CVE databases |
| MEDIUM | HackerNews, developer blogs |
| LOW | X, Bluesky, general social feeds |
Rule: Low-confidence signal never feeds the Council directly. Scout is a radar dish, not a judge — it surfaces "something is happening over there," not "this is true and Atlantis should act."
Downstream Consumers
This pipeline is the intake layer for: - Repo Radar (already live) - Threat Intel Bot (backlog) - YouTube Radar - AI Model Watch - Weekly updates.md compile - Chronicle intelligence section
Status
Drafted during the TN working session (Westgate Smoky Mountain, Vegeta), May 22, 2026. Confirmed approved by Shane (June 17, 2026) — cross-referenced and corroborated by CB-005's Council Decision Log Index, which lists CB-003 as "Active." This document's earlier "pending vote" framing, based solely on a June 5 status note that predated the actual vote, is superseded.
This document intentionally omits the internal design discussion that led to this architecture (including an early proposed "fused agent" identity that was reviewed and not adopted). Per Shane's direction, Council Brief documents record final architecture only, not internal deliberation history.