Use case
API-driven evidence collection
Submit simple target intent, poll bounded jobs and consume canonical objects through workspace-scoped keys.
Likely evidence
- Canonical result objects
- Evidence-backed findings
- Job progress and component state
Graph relationships
- Results retain canonical identities
- Findings reference affected objects
- Job owns one immutable plan
Expected outputs
- Cursor-paginated API records
- Stable request and job references
- Automated evidence handoff
Safety boundary
Evidence still needs judgment.
Keep keys server-side, use least scopes and preserve the same Idempotency-Key on uncertain retries.
This workflow is explanatory, not a scan profile or guarantee of discovery. Target compatibility, registry readiness, configuration, scope and budget determine the exact plan.
Start with a target
Turn this workflow into an explainable investigation.
Create an account to plan your first evidence-backed investigation, or talk to us about team and workflow requirements.