Scout (Second-Brain)

wiki/syntheses/downstream-consumers-and-project-relationships.md

Scout — Downstream Consumers And Project Relationships

Last Updated: 2026-06-29

Scout is the acquisition and evidence layer. It should not become every consuming product's analysis brain. The durable relationship rule is:

Scout acquires, structures, cites, and exports evidence. Consumers interpret and decide.

Relationship Map

flowchart LR
  Scout["Scout\nacquire + extract + evidence + exports"]
  PRISM["PRISM / Chowmes-PRISM\nsales coach + audit interpretation"]
  CI["Competitive Intelligence\nsource monitoring + acquisition benchmarking"]
  Audit["Algolia Search Audit Skills\ncompany/industry/competitor modules"]
  Catalog["Product Catalog Workflows\nAlgolia + JSON/CSV/SQLite/Sheets exports"]
  Jobs["Job Hunter Workflows\ncareers + ATS/job acquisition"]
  Website["Scout Website\nprivate beta education + onboarding"]

  Scout --> PRISM
  Scout --> CI
  Scout --> Audit
  Scout --> Catalog
  Scout --> Jobs
  Website --> Scout

Consumers

Consumer	Use of Scout	Scout capabilities consumed	Boundary
PRISM / Chowmes-PRISM	Runs acquisition before the Hermes sales coach answers questions or builds prospect deliverables.	`/scrape`, `/structure`, `/harvest`, source pages, citations, company/news/careers/investor evidence.	PRISM interprets and coaches. Scout does not generate sales strategy.
Competitive Intelligence	Uses Scout as a measurable acquisition primitive when it beats or complements direct HTTP/RSS.	Shared `/scrape` route, raw/clean markdown, final URL, provider, content hash, quality score, recommended collector.	CI owns source configuration and collector routing. Scout may recommend but not update CI source strategy.
Algolia Search Audit skill suite	Uses Scout for web evidence in company, industry, competitor, financial, hiring, investor, news, social, partner, and tech-stack modules.	Local HTTP API, skill backend, Crawl4AI-backed extraction, source evidence.	Skill modules decide what the evidence means for Algolia sales plays.
Product/catalog workflows	Converts ecommerce category/product pages into records for search experiences.	`/products`, product records, objectID strategy, Algolia preview/push, JSON/JSONL/CSV/SQLite/Google Sheets export bundles.	Scout prepares records; merchants/search teams decide merchandising rules and production indexing policy.
Job hunter workflows	Captures careers pages and job postings for filtering and scoring.	careers/jobs records, ATS evidence, artifacts, citations.	Profile matching, application strategy, and outreach are downstream logic.
Scout private beta website	Educates testers and routes them into local, Docker, hosted API, and skill usage.	Static website served by `scout serve`, `/quickstart`, `/guide`, `/examples`, `/pricing`, `/status`, `/beta`, `/legal`.	Website copy must follow the launch evidence index and cannot claim public launch readiness.

Current Product Surfaces

Local package and CLI: scout scrape, scout crawl, scout map, scout products, scout serve, launch-readiness helpers, product export helpers.
FastAPI service: core acquisition endpoints, run/artifact routes, hosted beta routes, public launch website routes, Swagger at /docs.
Docker service: local/self-hosted deployment with volume-backed artifacts.
Hosted beta API: finite-credit private beta, not unlimited crawling.
Skill backend: Claude/Codex usage pattern for agents that can call the local Scout server or package.
Website: launch/onboarding surface, not a replacement for the API docs.

Current Boundaries And Gaps

Private beta is allowed with limits; public launch is blocked.
Legacy /app UI is not certified as the product surface.
Hard-site/browser/user-session capture remains a beta capability, not a guaranteed bypass promise.
Public hosted launch still needs license, dependency risk, payment, terms/privacy, registry, and operational gates.
Intelligence verticals must be claimed feature-by-feature from validation reports, not from route existence alone.