---
title: "Boundaries and guardrails"
description: "Understand which actions a flow may perform and how uncertainty is reported."
canonical_url: "https://coldvisit.com/docs/guardrails"
md_url: "https://coldvisit.com/docs/guardrails.md"
last_updated: "2026-09-12"
---

# Boundaries and guardrails

Understand which actions a flow may perform and how uncertainty is reported.

## Approve the behavior, not just the name

Review each authored flow before approval. Its commit boundary specifies where execution stops before a consequential action. Opening that boundary requires an explicit choice and does not bypass the other enforced restrictions.

Some journeys need controlled account creation, test mail, or other test data. Review their disclosures and use dedicated testing resources.

## Healing stays within the flow

A proposed repair must preserve the target’s identity and respect data and boundary constraints. Automatic acceptance is limited to eligible changes; uncertain or forbidden repairs are not silently applied.

## Uncertainty is visible

A preview that cannot be reached or a session that has expired is reported as couldn’t run, with available context. ColdVisit does not label that condition as a proven application failure.

The gate is evidence about the selected flows on the tested preview. It is not a guarantee that every possible journey or environment is covered.