PR standards in AI era - own the test suite, not the code

Situation

In an AI-enabled world, engineers should own the test suite and exit criteria, not necessarily every line of code. Quality comes from tests passing, not from reading every line. Engineer accountability shifts from I wrote this code to I own that this code passes these tests.

Reasoning

Code is increasingly disposable and AI-generated. Engineers may submit PRs in languages they dont fully understand, with code they didnt manually write. The only thing that matters is whether it meets acceptance criteria. Testing ownership replaces code ownership as the accountability model.

Additional Context

Max frustrated that PRs go out without senior review, things ship with unknown quality. Peter reframing: in AI world, the bar for what engineer owns is changing. Rather than own every line, own the test suite and results.

Observed Evidence

Max: "I would much rather the engineer told me they read the test suite than that they read the code" and "Im submitting pull requests with my name on it that I cant tell you what every individual line of code does, and it doesnt bother me" and "What I want the engineer owning is saying, Im submitting this PR. Heres the tests... I have read the test suite. Ive reviewed the test suite."

Confidence Breakdown