1 min lesson
Gates, standard vs regulated and evidence at the red gate
Connect "A 'red' gate is blocking" to the decision you would make.
Step 1 of 2
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.
Interactive widget. Tab through its controls; the result updates in the panel below as you change them.
Commit → build → test → scan → review → stage → release. Build/tests, lint and review are red in most shops; SAST and secret scans turn red as shops mature; merge flows to staging, e2e, then progressive rollout. Each red gate blocks progression, and in regulated pipelines each blocking gate also emits durable evidence an auditor can later inspect: who ran it, what changed, when and with what result. Cursor's job is to make changes arrive at these gates smaller and already green, never to route around them.