We might categorize new code repos into one of three groups: Class 1: Fully reviewed: Every line is carefully reviewed and understood before being merged. All

We might categorize new code repos into one of three groups: Class 1: Fully reviewed: Every line is carefully reviewed and understood before being merged. All necessary edits are made. Class 2: Partially reviewed: Every line is looked at, but is not carefully reviewed or understood before being merged. Edits are sparse, if any. Class 3: Not reviewed (true vibe coding): Edits are not reviewed (outside of a major accidental deletion). The trust is altogether in the tests. Functional behavior is all that is reviewed. Granted, orthogonal adjustments to this grouping are possible, but imho it captures the essence of the process. The point is to classify each new repo at the time of its creation, then stick with it. Its classification should be documented in its readme.