5.1 Command-Line Architecture

The command-line layer connects BioLine platform objects with the local task-execution boundary.

• fkit discovers and inspects Flows, creates and queries Jobs, manages Tools, and exports or applies config and summary for an exact version.
• fkit command documentation exposes five options: --docs, --docs-index, --docs-link <path>, --docs-lang zh|en, and --docs-json. --docs always reads the index page fixed at https://www.bioline.cloud/ai/commandLineAndFkit/ and then fetches the corresponding Markdown from the same official AI service through the index mapping; --docs-index prints only the index itself, and --docs-link prints only the page behind one /ai/ path. Docs mode returns before login, required business-argument validation, or command execution and needs no BioLine login.
• OpenClaw host scripts record planning, confirmation, execution state, and reproducibility evidence by phase.
• Upstream Tools and Flows run in BioLine-hosted environments. Downstream execution uses an exact BioLine Tool version; OpenClaw pulls it on demand, creates a task-specific script, and runs it in an isolated environment with networking disabled.

A downstream script is not a fixed BioLine command. Before execution, OpenClaw checks the Tool summary/config: the summary declares analysis_lane: downstream and fixed_command: false, and the config contains no fixed analysis command. The task script, actual command, logs, and outputs are retained with the Tool version and pulled image identity. There is no need to preinstall the historical image set or select capabilities through a shared YAML catalogue.

Discover and reuse a suitable Tool or Flow first. If none fits, use the separate authoring workflow and confirm build, publish, and register independently.