Create a Flow

Flow authoring composes real Tool Versions into an inspectable directed graph. It is not a local script list and never guesses Tool IDs; every node and version comes from an fkit response.

Design constraints

• Load exact command pages needed for the operation and define inputs, file groups, and final outputs.
• Reference a real Tool Version ID for every node; keep parameter overrides on Flow nodes and never edit source Tools.
• Export config and summary for every exact node version; check port direction, required inputs, and parameter definitions.
• Use --flow-spec for the draft. Require method evidence: purpose, one ordered step and rationale per node, and at least one official or literature source. Step order must follow the graph's topological order.
• Support connections with a documented or official workflow method; file extensions alone do not establish compatibility.
• Preserve nodes, edges, source Tool snapshots/hashes, and method evidence in the authoring registry.

Flow and confirmations

A Flow needs no local image build. After drafted, run static port, required-input, parameter, DAG, and method checks before entering tested. After publish confirmation, run fkit flow create <FLOW_NAME> --file <PATH> in text mode; do not append --json. Accept only the exact success line Created flow '<name>', flowId=<id>, version=<positive integer>. Immediately run the read-only fkit flow list --keyword <FLOW_NAME> --limit 100 --json, resolve exactly one row by Flow ID and exactly one version entry by numeric version, and require its nonempty flowVersionId. Do not select by name alone or retry creation; missing, duplicate, or malformed readback is unverified failure. Preserve the resolved Flow and version IDs. After separate register confirmation, pass the expected FlowSpec to fkit flow inspect for read-back comparison. sourceGraph must provide enough server-side node, Tool Version, connection endpoint, port, and parameter-override data. Missing fields or incomplete endpoints fail verification; the local spec cannot substitute for server evidence. method remains local authoring evidence and is not sent as a backend Flow field.

Handoff

Only after both discoverability and Flow inspection pass may the registry enter verified and handed_off. The handoff records kind: flow, real IDs, keyword, and verification time. On the next execution, fkit dynamically queries and re-inspects the keyword instead of reading temporary authoring state.