VB-OS Flows: Post-Evaluation Pipelines

A flow is a directed acyclic graph (DAG) that defines what happens after a boundary evaluation. When a connector gathers evidence and the boundary returns a verdict, the flow executes the appropriate reaction: sending a webhook, logging an event, or triggering a notification.

How Flows Work

Connector gathers evidence
    ↓
Boundary evaluates → ASSERT or DEFER
    ↓
Flow executes the matching branch
    ↓
Actions fire (webhook, notification, log)

Flows are triggered automatically when:

1. A boundary evaluation completes (whether initiated by a connector with auto-evaluate or by a manual evaluation request)
2. An active flow deployment matches the evaluation’s environment, boundary reference, and boundary version

Flow Lifecycle

DRAFT → ACTIVE → ARCHIVED

A flow must have at least one approved version to become active. Archived flows can be reactivated.

Flow Versions

Each flow has immutable versions:

DRAFT → APPROVED

Only draft versions can be edited. Once approved, a version is immutable and can be deployed.

Flow Deployments

Deploy an approved version to an environment:

Status	Description
ACTIVE	Processing evaluations in this environment
SUSPENDED	Temporarily paused
SUPERSEDED	Replaced by a newer deployment

Only one active deployment per flow per environment.

Next Steps

• Flow Builder: node types and DAG structure
• Governed Dispatch: how flows execute
• Failure Behavior: error handling and retries