Handing an investigation to an agent
Save JSON and comparison conditions to produce an evidence-linked memo or weekly report.
When to use this workflow
“Prepare a weekly report with evidence I can trace.”
Before fetching
Establish the audience, decisions, dates, and handling of source data. Fix the source responses and conditions before asking the agent to summarize.
Quick reference
Save the inputs before handing them to your agent.
orc reports visibility get --json > visibility.json
orc reports citations get --json > citations.json
orc reports sentiment get --json > sentiment.jsonPrerequisites
Complete the CLI quickstart. These commands use CLI 0.5.0. Select the target workspace and use IDs returned by list commands.
Successful JSON exports and a memo recording measurement scope.
1. Define the scope
Provide the baseline JSON and a memo containing scope, periods, answer IDs, and citation URLs. For example:
2. Ask the agent
Read the saved reports and answers. Summarize what changed, the evidence, and what to check next.
Keep data with different comparison conditions separate and identify missing data.
Separate observations from hypotheses. Attach an answer ID or citation URL to each conclusion.3. Check and keep the result
In scripts, specify the workspace with --workspace and check command exit status before downstream processing. Share only the data needed for the task. Saving files does not configure scheduled execution or delivery.
When data is missing
If data is missing, check the workspace, collection period, filters, and pagination. Keep a failed request separate from an empty result. Use --help to inspect supported options.
If a failure remains, report it and verify the fix, including this workflow and the failed step.