Before you start
Use an authorized workspace and a small file with stable source IDs. Have source access and your team’s acceptance policy available. This guide describes customer-authored logic, not an automatically enabled product policy.1. Understand the decision
A target market is a business definition. A provider query returns a population under its own coverage and filters. Test this fictional sample before calling providers:2. Inspect supported operations
deepline describe <returned-id> --json.
Compare required identifiers, outputs, access mode, and price.
A similar title does not establish that a contract fits.
3. Implement the bounded workflow
Ask your agent to authortam-enrichment.play.ts using Write Plays.
Have it declare the CSV input and preserve source IDs.
Reuse existing contracts when they fit the transformation.
Implement these rules explicitly:
- Define inclusion, exclusion, geography, and the company entity being counted.
- Preserve source identifiers and query coverage limits.
- Enrich only the fields required by the inclusion rule.
- Keep qualified, excluded, and unresolved accounts separate. Missing coverage is not proof of exclusion.
4. Check and pilot
Preparepilot.csv using CSV-safe selection.
Then check the source:
5. Verify the outcome
Reconcile account identities and inclusion evidence. Report source scope alongside counts instead of calling the export the entire market.Every source ID has a result or explicit exception. The fictional cases follow
the stated policy, and actual results retain their evidence.