Decision Log — Scout Leadership Intel

ADRs go here. One file per decision. Filename format: YYYY-MM-DD-decision-name.md

Template

Decision: [Name]

Date: YYYY-MM-DD Status: Accepted / Superseded / Rejected Context: Why this decision was needed Decision: What was decided Alternatives considered: What was rejected and why Consequences: What changes as a result

Decisions Made at Spec Time

Decision: Map-First (no URL guessing)

Date: 2026-05-05 Status: Accepted Context: Eval data showed standard leadership URL paths (/team, /leadership) frequently return 404s across different company sites. URL patterns vary too widely to hardcode. Decision: Always call /map on the domain before any /scrape call. Never attempt a scrape on a guessed URL. Alternatives considered: Hardcoding a priority list of URL patterns and attempting each in sequence without mapping — rejected because it generates unnecessary requests and fails silently when none match. Consequences: Map call adds ~10–45s to every run, but eliminates false 404 failures and enables full URL discovery.

Decision: Source Attribution is Non-Negotiable in MVP

Date: 2026-05-05 Status: Accepted Context: Stale executive data (from press releases vs. current leadership page) was identified as worse than no data — it creates false confidence before sales calls. Decision: Every row in the output table includes a Source column with the URL it was scraped from and the crawled_at timestamp. Fallback data is visually distinguished from authoritative data. Alternatives considered: No source column (cleaner table) — rejected because the AE persona requires trust signals before acting on the data. Consequences: Output table has 3 mandatory columns (Name, Title, Source) instead of 2.

Decision: Partial Results Over Silent Failure

Date: 2026-05-05 Status: Accepted Context: Some companies have no dedicated leadership page. Returning nothing is less useful than returning what was found with a warning. Decision: If exec data is found in a fallback source (press release, About page), return it with a visible WARNING banner. Never return empty silently. Alternatives considered: Return nothing unless a dedicated leadership page is found — rejected because BDR persona values any name over no name. Consequences: Fallback flow (F1, F2) must be implemented as part of MVP, not fast-follow.