Author a private Firedrill service

Model the application's dependency seam, not its decision logic. Inspect the actual operations it uses, the state transition needed for the scenario and the limits of the proposed model. Reuse a suitable saved build before authoring one. Do not imply native vendor protocol fidelity from semantic HTTP/MCP support.

Use the installed firedrill tools help and the packaged source, manifest, dataset and qualification workflow. That reference includes one complete replaceable example; adapt its semantics to the user's dependency, not just its names. Read the bindings guide only when attaching the qualified build to an application or sequence.