Glossary
Every platform term in one place — grouped by concept cluster, then listed A–Z for lookup.
The terms below are grouped the same way Concept clusters groups them, then repeated A–Z for quick lookup. Each definition matches how the term is used across these docs.
By cluster
Surfaces — where you work. Ivy, .bloom* studio, ivybloom CLI.
Work units — what you run. Tool, Workflow.
Execution — how a run happens. Job, Batch, Artifact.
Results — what you get back. Canvas card, Passport.
Organization — how work is grouped. Campaign, Session, Checkpoint.
Naming — what the names mean. Ivy Biosciences is the company. .bloom* is the platform you work in. Ivy is the agent that does the work. ivybloom CLI is the scriptable surface. pleach is the underlying runtime. These five are used consistently throughout the docs; when a page says "the platform" it means .bloom*.
A–Z
.bloom*
The platform — the tools, orchestrator and record behind every run. You reach it through Ivy, the .bloom* studio, the ivybloom CLI, an MCP client, or a curl request; all of them hit the same backend. When these docs say "the platform," they mean .bloom*.
.bloom* studio
The project-based surface — a file explorer, job dashboard, and canvas for direct control over parameters and layout. See Studio.
ADMET
Absorption, distribution, metabolism, excretion, and toxicity — the pharmacokinetic and safety properties a compound must clear to be a viable drug. Predicted by tools such as ADMET-AI; ADMETLab3 is retired.
Artifact
A file a completed job produces — PDB for structures, SDF for molecules, CSV for tables, PNG for plots. Downloadable and exportable from the card.
Batch
Many jobs submitted together. A batch holds at most 100 jobs, on the web and in the CLI.
Campaign
A project-level grouping of related chats that share an objective, with aggregated job history and canvas. See Campaigns.
Canvas card
The interactive result of one job. Expands through four tiers — text, preview, interactive visualization, and floating window. See Canvas.
Capability inference
How the orchestrator maps a plain-language goal to the tools that provide the requested capability, without you naming the tools. See How the orchestrator picks tools.
Checkpoint
An immutable snapshot of session state at a lifecycle event. Roll back to a checkpoint to discard everything after it. See Checkpoints.
Completeness score
A 0–100% measure of how much data a passport found across its sections. A low score marks thin sources, not failure.
Ivy
The agent. You give Ivy a goal in plain language; it plans the run, picks and chains the tools, runs them, cites the results, and — in interactive web and terminal sessions — asks you when it needs a decision. You reach Ivy from the web app, the ivybloom TUI, an MCP client, and POST /api/v1/orchestrate. See Chat.
Ivy Biosciences
The company that builds and operates the .bloom* platform. Use the full name for the company or legal entity; use .bloom* for the product itself.
ivybloom CLI
The scriptable surface — commands for batch processing, CI/CD, and reproducible pipelines. Shares one backend and job history with Ivy and the .bloom* studio. Written ivybloom (lowercase) in prose, the same as the binary you invoke, ivybloom. See CLI.
Job
One tool invocation with inputs. Moves through queued → running → completed (or failed / cancelled). Draws down your monthly credits.
Orchestrator
The AI that reads your goal, selects tools, chains them, and streams results. See How the orchestrator picks tools.
Passport
A multi-source aggregated report keyed to one subject. Five core types — compound, target, safety, literature, therapeutic area. See What a passport is.
pleach
The agent runtime that powers orchestration underneath the .bloom* platform — session state, tool execution, checkpoints, and streaming. You rarely touch it directly from these docs; its SDK and developer narrative live at getpleach.com.
Session
The persistent container for one multi-turn conversation — messages, tool calls, pending and completed jobs, checkpoints. See Harness sessions.
Tool
A single computational capability — ESMFold, DiffDock, REINVENT4. Runs as a job or an instant lookup, returns structured results, renders as a card. See Which tool?.
Turn
One exchange in a session — your message, Ivy's response, and any tool calls it triggers.
Workflow
A guided, documented multi-tool pipeline — prerequisites, steps, expected outputs, best practices. You run each step. See Workflows.
Was this page helpful?