Build a workflow
Simulation
Inspect a workflow before committing, and understand what a preview can and cannot establish.
On this page
Simulation is bound to a revision
Simulation consumes the selected path’s quotes and observed state. Its hash-linked artifacts feed policy, the Strategy Manifest and the execution plan. Quotes and state can expire; material workflow edits invalidate downstream references.
A read-only server preview
const preview = await flofi.strategies.simulate(strategy.id, {
simulationSubject: userAddress,
});
// preview: true, persisted: false, authorizable: false
// authority: "NONE"typescriptThe subject is a public address whose state the preview reads. It is not authenticated wallet ownership and grants no authority. The Developer API preview does not expose calldata or signatures. Multi-step API previews are refused with SIMULATE_ONE_STEP_AT_A_TIME.
Refresh before review
- Check provenance, freshness and any limitations.
- Resolve blocking findings.
- Re-simulate after material edits or quote expiration.
- Review the new Strategy Manifest.
MOCKED previews retain MOCKED provenance. A successful preview cannot upgrade evidence to testnet or mainnet execution.
These guides summarize the repository’s current contracts. Detailed evidence and engineering history stay in their original records.
docs/developer/API.md docs/developer/QUICKSTART.md docs/contracts/INVALIDATION_V1.md