Virtual environments preserve StreamBuild’s versioned deployment workflow. Enable them for the
whole invocation:
The lifecycle is:
Backfill
Backfill creates deployment-specific model objects while the active stable views remain unchanged:
The deployment ID is generated as YYYYMMDDTHHMMSSZ_<six-hex> unless supplied with
--deployment-id.
Assess staged data
Assessment compares staged and active data, checks replay coverage, and runs applicable SQL audits.
Error-severity quality failures produce a not_ready assessment. Warning-severity failures appear
in the audit results but do not by themselves change the replay-readiness assessment.
Assessment is an operator safety step, not an enforced publish lock. stb publish does not
require a previously persisted ready result.
Publish
Publish creates or replaces stable views such as tbl__orders to read from the selected deployment
table. ClickHouse replaces each relation atomically, but the complete graph is not graph-atomic:
bindings are switched one relation at a time and StreamBuild reports that capability in output.
Candidate selection
For audit backfill and publish, omitting --deployment-id works only when exactly one candidate
is available. Zero candidates is an error; multiple candidates produce explicit commands to choose
from.
Operational commands
doctor diagnoses stable-view and deployment-reference problems.repair active-view points one broken logical view at a known deployment.reconcile previews or records a compatible live metadata baseline.janitor previews or removes stale deployment objects while protecting active and
recent state.
These commands are virtual-environment-only. There is no automatic mode conversion or direct-mode
equivalent. 
