ADR-0001: Scout Scope Boundary

Date: 2026-06-12 Status: LOCKED Decision: Scout = acquire + extract. PRISM/skills = interpret. Scout never has an opinion.

Context

Scout started as a web scraping tool embedded in PRISM's intelligence modules. As it grew, the question arose: should Scout interpret the data it acquires (e.g., score competitors, evaluate tech stacks)?

Decision

Scout owns acquisition and extraction only. It returns verbatim/structured/cited content. It never interprets, scores, or recommends. Intelligence verticals are CONSUMER specs, not Scout features.

Consequences

• PRISM intel modules import Scout for data, then apply their own interpretation logic.
• scout.core never imports a consumer module.
• Scout's API surface is target-agnostic — it works on any website, not just PRISM's use cases.
• 9 intelligence use cases (/run/{use_case}) are consumer-defined, currently stubs.