Code review dans le SDLC augmenté : l'anneau de contraintes autour des agents
Episode « Phase 5 · Review » of SFEIR's series on the augmented SDLC, published **the same day** as Addy Osmani's LinkedIn post, which it translates into a phase specification. Thesis: **quality has changed address** — it is no longer read in the code (agents produce more of it than anyone can review) but in **the ring of constraints surrounding the agent**. Osmani's ring (seven dimensions — correctness, security, performance, accessibility, maintainability, **economic efficiency**, **understandability** — linked by the **back-pressure** rule: "a loop is granted only the autonomy one knows how to verify cheaply and reliably, not an inch more") is redrawn, translated, and attached to phase 5 of SFEIR's 11-phase cycle. The structuring corollary: **the bottleneck was never generation, it is verification** — "generation is a wide mouth, verification a narrow neck; speeding up the mouth thickens the pile at the neck." **The most interesting design decision is a cycle-architecture choice**: Review is deliberately **outside the three human gates** (Define, Plan, Ship), because putting the gate on Review would amount to placing human attention — a finite resource — as the checkpoint of a generation capacity that, itself, scales: "you would have built a pipeline whose maximum throughput is the number of diffs a senior can read before the end of the day." Hence the split: **Review instruments, Ship decides** — Review delivers an *opposable body of evidence*, Ship decides on the evidence, not on the full diff. A position taken against Monperrus (whose diagnosis SFEIR keeps — human inspection of every diff does not withstand agentic speed — but whose conclusion it rejects: acceptance cannot be delegated). The named trap is **circular validation** (the agent that writes the code writes the tests that validate it: "you have built a mirror, not a ring"), with five countermeasures borrowed from Anthropic (independent gates in separate context windows, deterministic + agentic never substituting for one another, shadow mode, risk-based tiering, logging to the SIEM) and Compare the Market's warning (**AST graph ~70% vs vector RAG ~58%**, RAG performing *worse than no context at all*). The firm's own extension is **the ratchet**: "every escape becomes a constraint" — a defect that has crossed the ring is closed back up *inside the ring* (test, lint rule, rubric, harness guardrail) at Compound-1, "the only asset in the chain that appreciates while models depreciate" (an internal, unauditable measure: **− 30% fewer correction iterations after ten cycles**). It closes by reformulating the question: "is this code good?" has become unanswerable; what remains is **"what does my system refuse to let through?"**
SFEIR (voix éditoriale du cabinet, article non signé individuellement) — construit sur Addy Osmani (Google) ; cite Martin Monperrus · Paula Hingel (Augment Code) · DORA/Google Cloud · Jason Clinton (Anthropic) · l'équipe Engineering de Compare the Market