Skip to main content
Human guide: work with your agent → Build a small account brief that separates sourced facts from hypotheses. Keep enough evidence to review each proposed outreach angle.

​
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

An observation needs its source and scope. An inference must remain distinct from an observed fact. Test this fictional sample before calling providers:

​
2. Inspect supported operations

Inspect a returned ID with 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 author account-research-automation.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:
  1. Define the account identity and three bounded research questions.
  2. Retain source URLs, retrieval time, and available observation dates.
  3. Connect findings to evidence. Mark unsupported conclusions as hypotheses.
  4. Return missing evidence and the next question without creating outreach or CRM changes.
Keep external changes disabled for the first pilot. That control belongs in the authored logic, not a universal Play dry-run flag.

​
4. Check and pilot

Prepare pilot.csv using CSV-safe selection. Then check the source:
Resolve authoring errors first. After reviewing source and price, run only the pilot:
Use the ID returned by the pilot. Select a returned dataset path when several exist. Provider-backed execution can incur usage.

​
5. Verify the outcome

Open the evidence behind each conclusion. Confirm that unavailable access did not become a claim that no activity exists.
Every source ID has a result or explicit exception. The fictional cases follow the stated policy, and actual results retain their evidence.
Ask your agent why a record was accepted, held, or rejected. Correct the rule before expanding input or enabling external writes.

​
Continue

Research workflow covers sources. Provenance explains evidence history.