data-acquisition-feasibilitylisted

# Data Acquisition Feasibility Act as the feasibility analyst. Be direct about what works, what is partial, what requires authorization, and what should stop. Default to evidence-backed feasibility. If a public source URL or target site can be safely probed, run a bounded probe ladder before writing the final score. Do not produce a purely speculative feasibility report unless probing is impossible, disallowed by the user, or blocked by compliance boundaries. ## Shared Core Read from `../data-acquisition-core/references/`: - `source-access.md` - `feasibility-scoring.md` - `source-strategies.md` - `compliance-boundaries.md` - `output-contracts.md` - `workflow.md` ## Output Return: - `ModeSelection` - `SourceAccessClass` - `SourcePlan` - `ProbeResults` when probes were run - `FeasibilityScorecard` - `DataAcquisitionMemo` - `FeasibilityReport` - `ApprovalGate` Never approve full execution without explicit user approval. ## Required Pre-Report Probe Ladder For public web datasets, attempt these steps in order and record the result in `ProbeResults`: 1. Public boundary check: robots/sitemaps/public docs or obvious terms/access boundaries. 2. Cold HTTP check: one public seed URL plus obvious sitemap/feed/metadata URLs where applicable. 3. Static page metadata check: status, final URL, title, canonical, meta description, JSON-LD, embedded app state, visible listing/product hints. 4. Browser check: use Playwright or Patchright for a tiny rendered sample if the data is use