Workflow Cookbook
Short operator recipes for common Dreadnode jobs: where to start, what to check, and what artifact to keep.
This section is a cookbook, not a product tour. Each page is meant to answer four practical questions quickly:
- where to start
- what you need before you start
- what to inspect when the workflow gets ambiguous
- what durable artifact to keep when the work is done
How to use the cookbook
Section titled “How to use the cookbook”- choose the page by the job in front of you, not by product surface
- follow the shortest recipe first, then open the linked reference pages only if you need exact flags, schema details, or deeper concepts
- keep the same organization, workspace, and project context from start to finish so transcripts, traces, evaluations, and analytics all line up
Common Rules
Section titled “Common Rules”- keep IDs as you go: session IDs, evaluation IDs, assessment IDs, runtime IDs, and capability versions are the handles you need later
- save one representative failure before widening the investigation
- promote the result into a durable artifact when the workflow is stable: dataset, capability version, evaluation, assessment, or saved query
Quick Chooser
Section titled “Quick Chooser”| If you need to… | Start here | Switch when… | Keep |
|---|---|---|---|
| Probe a model or agent for jailbreaks, tool abuse, or exfiltration | dreadairt in the TUI or dn airt run | you have one reproducible attack path | assessment IDs, winning prompts, follow-on eval dataset |
| Test a web app inside isolated compute | web-security capability in a runtime | you have one verified finding or reusable check | transcript, traces, scoped notes, task or evaluation candidate |
| Run a repeatable security regression | dn evaluation create or the evaluation UI | one sample needs deeper transcript or trace review | evaluation ID, failing sample IDs, analytics query |
| Improve a capability with pinned inputs | published capability + published dataset | the job finishes with a candidate worth promoting | optimization job ID, promoted capability version, follow-on eval |
| Debug one suspicious conversation | reopen the session first | you know which run, span, or runtime state matters | session ID, trace evidence, exact repro step |