A workflow is a reusable sequence of steps that produces a known outcome. BreezThru ships with assess_offer, which gathers a target, verifies the company, and drafts a client-facing offer.
A run is one execution of a workflow. Steps are the individual tasks inside that run.
An L2 step is promoted to L1 only after passing scenario and corpus evaluations below a failure-rate threshold. Promoted steps are spot-checked and monitored for drift.
A sample of a promoted step's outputs is routed back for human review. Spot-check acceptance is tracked and feeds the step's health.
A promoted step "drifts" when its prompt, model, or acceptance changes. It falls back to L2 until resolved.
No. Runs are created from a schema-driven form, targets are managed in a UI, and Search answers questions in plain English.
In the Queue (/admin/queue): approvals, manual steps, and spot-checks.
Yes. Every decision, change, and run is recorded, with an audit trail on each target's page and queryable from Search.