Project structure

Keep your application’s existing layout. Add only the integration files needed for its execution seam.

File	Purpose
`firedrill.config.json`	Selected project and environment; no token
A recipe JSON file	Target, scenarios, configurations, repetitions, optional Tool bindings
A simulation script	Calls the native SDK and your actual agent entry point, if needed
A target adapter	Translates command/HTTP input and Tool bindings into the application’s existing interface
Explicit dataset files	Synthetic starting records you choose to upload
A CI workflow	Reuses the recipe or native simulation script

A private synthetic Tool may have its own manifest, deterministic behavior source, view, data, and conformance cases. It is separate from the application being simulated. Keep secrets and private recovery journals out of version control. You can commit reviewable scenarios and their checks without putting the evaluation criteria into the target’s task input. See simulation files and Tool authoring.

Get started

Coding agents

Simulations and evidence

Synthetic Tools

Automation

Web app and access

Core concepts

Files and reference