liveBook · Manning

Quality gate

As explained in Vibe Engineering

A quality gate is a defined checkpoint that requires specified quality criteria to be satisfied before work can proceed.

A quality gate is a defined checkpoint that requires specified quality criteria before work proceeds. In agent-driven development, it keeps orchestration from becoming a license to ship unchecked output. section 5.7

The gate belongs inside the Software Development Lifecycle, alongside sandboxing, rollback procedures, observability, and incident response. It shifts engineering from producing every function to judging whether system output remains acceptable. section 5.7

Use a quality gate to:

  • Define what good looks like before agents or pipelines advance work. section 5.7
  • Inspect output drift and intervene when orchestrated components stop meeting expectations. section 5.7
  • Pair acceptance checks with rollback and observability when automation increases operational distance. section 5.7

How Vibe Engineering covers it

How deep it goes
Explains the operational role of gates but stops short of specifying criteria, tests, or approval procedures.
Examples
Uses orchestrated agent fleets, sandboxing, rollback procedures, observability, and incident response as operational contexts.
What it assumes
Assumes engineers can recognize acceptable output and understand the operational risks of orchestrated automation.
What you can do after
Operate agent workflows by defining acceptance checkpoints and intervening when output drifts.
How it connects
Connects quality gates with agent workflows, observability, rollback procedures, incident response, and feedback loops.

Also explained in

Compare how 9 books explain quality gate →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.