1.2 BioLine: A Standards-Aware, Traceable Analysis Collaborator

BioLine manages reusable analysis capabilities as platform Tools and Flows. Upstream Tools are hosted by BioLine and run through stable commands; a Flow organizes inspected Tools, input ports, and parameters into a cloud Job. Downstream statistics, machine learning, plotting, and reporting are also provided as exact BioLine Tool versions. They do not depend on a repository-local plug-in directory or a static capability catalogue.

OpenClaw first discovers existing Flows or Tools and checks their versions, interfaces, and documentation. Downstream execution uses an exact NAME:VERSION and exports that version’s summary and config. The summary must declare analysis_lane: downstream and fixed_command: false, and the config must not contain a fixed analysis command. OpenClaw then pulls that Tool version on demand, generates and saves a task-specific script, and executes it in an isolated environment with networking disabled. Stage inputs are read-only and the task analysis directory is writable. Users do not have to build or install the historical image set in advance.

If no suitable capability exists, the user can create a Tool, Tool Version, or Flow through the separate authoring workflow. Build, publish, and register each require confirmation; the object is handed to execution only after server read-back verification. The five historical local downstream images are migration inventory, not runtime choices.

Traceability records the real Flow and Job, exact Tool version, summary/config snapshot or hash, generated script, pulled image identity, actual command, logs, and outputs. The model interprets requests, presents plans, and coordinates stages; BioLine hosts platform Tools and Flows, while task scripts run only inside the defined local isolation boundary.