Review council

A review council swaps one automated reviewer for a panel. One pass hunts security holes. Another checks the change against its spec. Another looks for over-building or dead code. Each reviewer runs with fresh context and a narrow brief, so one stance covers another's blind spots.

The pattern exists because a single model tends to give one flavor of feedback. It also goes easy on work that resembles its own. Rotating stances helps. So does using a second model for the hostile pass. Both surface bug types a lone reviewer misses.

Councils cost money. More reviewers mean more spend, more delay, and more findings to sort. The design question is where the panel pays for itself. Usually that means changes touching auth, money, data migrations, or public interfaces.