Skip to content

4.4 Discover BioLine Tools and Flows ​

This page keeps its existing URL. Analysis capabilities are supplied as BioLine Tools or Flows; OpenClaw does not maintain a local pipeline, Tool, or analysis-component selection catalogue.

Discover Flows ​

Search dynamically with fkit flow list, then use fkit flow inspect to check the real version, ports, parameters, edges, and node overrides. Plans use only IDs returned by BioLine. If several candidates are similar or graph read-back is incomplete, show the gap and stop rather than guessing from a name.

Discover downstream Tools ​

Search existing Tools for the objective. For each candidate, export summary/config for the exact NAME:VERSION and check supported inputs, resources, and outputs. A downstream summary must declare analysis_lane: downstream and fixed_command: false; config command fields must be empty or absent. Pull the version only after confirmation, then generate and run a task-specific script offline.

The five old local downstream images are migration inventory only. They do not need to be installed in advance; image cleanup follows the task pull ledger and identity checks.

When no suitable object exists ​

Check live discovery results and documentation first. If no Tool or Flow meets the objective, use the separate authoring workflow to create one on demand and complete static checks, independent confirmations, and server read-back verification. If authoritative interface or documentation is missing, record document_gap instead of inferring capability from a historical name.