lead-genlisted

# Axon Lead Gen Use this to extract legitimately accessible prospect lists. ## Onboarding Interview Infer the prospect target, source, lead count, and output format from context. If the target is clear, proceed immediately. Ask at most 1-3 concise questions only if blocked, such as the prospect definition, source/auth requirement, or target lead count. ## Axon Collection Plan Use `axon search`, `axon research`, `axon scrape`, `axon map`, and `axon extract` for public or authorized sources. For filters, forms, pagination, or login, use separate browser automation only when the user confirms authorized access and source terms permit automated extraction; feed discovered URLs/content back to Axon. For finished lead-list deliverables, run Axon commands in blocking mode: `axon extract ... --wait true --json` and `axon <source> --wait true` (add `--scope site` for a directory section). All indexing goes through that one source command — there is no `axon crawl` or `axon ingest`. Axon has **no robots.txt enforcement flag**; keep public-source capture bounded with `--max-pages`, `--max-depth`, and `--budget PATH=N`, and honor the source's terms. Do not collect personal contact info unless the user confirms lawful basis and source terms permit it. Do not infer, enrich, guess, de-obfuscate, or use scraped personal data for unsolicited outreach. Exclude sensitive/protected traits and minors. Include source, basis, suppression/opt-out notes, and limitations. Apply filters such a