---
id: "action-implement-comprehension-gate"
type: "action-item"
source_timestamps: ["00:13:09", "00:13:50"]
tags: ["code-review"]
related: ["concept-comprehension-gate", "concept-comprehension-gap", "framework-dark-code-solution"]
speakers: ["Nate B. Jones"]
action: "Require senior engineers to review AI PRs strictly for architectural legibility and intent, rejecting unexplainable code."
outcome: "Stops dark code from entering production and forces AI generation to optimize for human readability."
sources: ["s23-amazon-16k-engineers"]
sourceVaultSlug: "s23-amazon-16k-engineers"
originDay: 23
---
# Implement a Comprehension Gate

## Action

Modify the PR review process for AI-generated code to include a **Comprehension Gate**. Senior engineers review code not just for functional correctness but to ask:

- *Why* did the AI place this dependency here?
- *Why* is this caching at this layer?
- *Why* this data structure rather than another?
- Can I, the reviewer, explain this code to another human in plain language?

If the answer is unclear, **reject the PR — even if all tests pass.**

## Outcome

- Stops [[concept-dark-code]] from entering production
- Creates selection pressure that forces AI generation to optimize for human readability over time
- Closes the merge-time side of the [[concept-comprehension-gap]]

## Implementation Notes

- Tag PRs with an `ai-generated: true` label so reviewers know to apply the gate.
- Document explicit grounds for rejection that go beyond test failures (e.g., 'reviewer cannot explain this control flow').
- Pair with first-pass automated tooling (linting, security scanning, AI code review tools) so the senior engineer's time is reserved for architectural intent — addressing the bottleneck critique noted in the enrichment overlay.

## Connects To Concept

This is the direct operationalization of [[concept-comprehension-gate]] — Layer 3 of [[framework-dark-code-solution]].