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 title suggests responsibility. It does not establish budget authority or support for a purchase. 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 authorbuying-committee-mapping.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 the account and the buying roles you need to understand.
- Resolve people and current company relationships from inspected contracts.
- Retain role evidence. Mark inferred authority as unconfirmed.
- Identify missing roles and the next introduction or question without inventing contacts.
4. Check and pilot
Preparepilot.csv using CSV-safe selection.
Then check the source:
5. Verify the outcome
Check current employment and evidence for each buying role. A useful map can still have an unknown budget owner.Every source ID has a result or explicit exception. The fictional cases follow
the stated policy, and actual results retain their evidence.