Workflows and Cells

Shared vocabulary for governed act: workflows, runs, compileHash, and where cells run on hosted or cluster paths.

Open workflowsOpen runs

This page is the vocabulary chapter. Docs, the console, and the SDK use the same words for workflows, runs, and cells. For hands-on steps, start with Run first workflow. After Security, use this page when you need definitions, not operations.

Infer, decide, and act

Your stack keeps infer and decide logic. Blekline focuses governance on act, where tools run and side effects happen. API and SDK runs set executionTier: act when you record governed execution against a workflow.

TierWhere it runsMeaning
inferYour stackReasoning and planning in your code or orchestrator. Not metered as act run-minutes.
decideYour stackBranching and routing before side effects. Not metered as act run-minutes.
actGoverned by BleklineTools run and side effects happen. Use executionTier act for workflow runs and cell-backed paths.

Workflows

A workflow is a governed act identity in Blekline, not a generic orchestration DAG. It has a stable wf_ id, optional policy defaults, and a home in Workflows. Register from the console or your orchestrator. See Run first workflow for registration snippets.

Runs

A run is one invocation of a workflow. Each row in Runs stores status, placement, duration, and compileHash at birth. Proof and investigation live in Audit & metrics. Terminal states and timestamps are covered in Run lifecycle.

Policy snapshot

Published runtime policy compiles to a bundle with a single compileHash. Runs capture that hash when they start. Changing published policy does not rewrite history on older runs. Author and publish on Runtime policy; verify with the SDK or policy stream API.

Cells and placement

Fast act uses hosted runtime on Platform Team. Isolated act uses cells in your cluster on Platform Production. Only act paths that launch a cell count toward act run-minutes. See Billing & limits and Spin up cells.

ModePlanWhere act runsConsole
Fast actPlatform TeamHosted Blekline runtime (no clusterId on the run).Runs, hosted compute targets
Isolated actPlatform Productioncells in your VPC.Compute, cell profiles

Glossary

TermMeaning
CellIsolated execution environment for act paths. Platform Team uses hosted runtime; Production uses cells in your cluster.
WorkflowRegistered act path (stable wf_ id) with policy defaults. Create in the console or register from your orchestrator.
RunSingle invocation of a workflow. Inherits a compiled runtime policy snapshot at birth (compileHash).
Runtime policyPublished guard set from the control plane. Every run records which compileHash was active.
Act pathWhere tools execute and side effects happen. Blekline governs act by default.
compileHashFingerprint of the published policy bundle evaluated when the run started.

Console map

Objects in the app

Primary and Protect rails for act identity and policy.

Primary

  • WorkflowsRegister act paths and policy defaults for repeated execution.
  • RunsStatus, compileHash, and placement for each act invocation.
  • ComputeConnected clusters and hosted runtime targets.
  • Cell profilesCapacity and isolation settings for cluster act.

Protect

How it fits together

  1. Define or register a workflow (wf_ id) with policy defaults.
  2. Start a run with executionTier act.
  3. Hosted or cluster placement launches a cell when the profile requires it.
  4. Mask and enforce apply on the path using the same compileHash as published policy.
  5. Audit rows and run metadata tie proof back to that hash.

Hooks and MCP can enforce policy on ingress without a run row. Workflow runs are the product identity for hosted and cluster act you meter, audit, and operate as a unit.

Related guides