liveBook · Manning

Triage threshold

As explained in Vibe Engineering

A triage threshold is a configured criterion that assigns work or changes to review and automation risk levels.

A triage threshold assigns modules to Green, Yellow, or Red risk tiers, determining what may enter review queues or qualify for safe auto-merge. section 10.8.2

Treat thresholds as calibrated engineering policy, not a shortcut to speed. Start modules at Yellow, then promote patterns to Green only on evidence; the argument over those decisions exposes architectural judgment. section 10.8.2

Repository risk-tier artifact

Record three modules, their Green/Yellow/Red tiers, and one owner per module in a repository file reviewed like code. section 10.8.2

How Vibe Engineering covers it

How deep it goes
Defines three risk tiers and recommends starting at Yellow, promoting patterns to Green only on evidence.
Examples
Uses a repository artifact assigning three modules to Green, Yellow, or Red tiers with one owner each.
What it assumes
Assumes deep architectural understanding of module stability and the risks of automated changes.
What you can do after
Operate review queues by assigning module risk tiers and promoting automation only after evidence.
How it connects
Connects code organization, AGENTS.md, review queues, module ownership, and safe auto-merge decisions.

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.