Skip to lesson
Exit
CI/CD, release engineering & the toolchain1 / 3

2 min lesson

Gates, standard vs regulated and evidence at the red gate

Rebuild the sequence in "Gates, standard vs regulated and evidence at the red gate" from memory, ending with the check that proves the outcome.

Step 1 of 3

A pipeline is a sequence of gates: automated checks a change must pass to advance. A 'green' gate is permissive, fast and advisory. A 'red' gate is blocking. The change cannot proceed until it passes and in regulated shops it must leave behind evidence that it passed.

The gap between a standard pipeline and a regulated one is the core of speaking to enterprise buyers.

Anatomy of a change pipeline, with red gates and evidence

Interactive widget. Tab through its controls; the result updates in the panel below as you change them.

diagram: pipeline

Commit → build → test → scan → review → stage → release. Each red gate blocks progression; in regulated pipelines each blocking gate also emits durable evidence (who, what, when, result) an auditor can later inspect. Cursor's job is to make changes arrive at these gates smaller and already-green, never to route around them.