Name: Tested Interpretation (normative): A meaningful automated test suite gates changes, giving an agent a verifiable signal that an edit did not break behaviour.
At L2 the codebase has a verifiable signal. A meaningful automated test suite runs on every change, end-to-end tests cover the critical journeys, and coverage is held to a real threshold. An agent arriving at an L2 repository can make a change and know — not guess — whether it broke something, because the suite turns "it looks right" into "it is proven green."
L2 is where agent-assisted maintenance starts to feel safe. The test suite is the contract the agent leans on, and the surrounding gates — error aggregation, documented runbooks, branch protection — mean a regression is caught rather than silently shipped. It is functional and resilient, even if standards are not yet fully enforced across every contributor.
Criteria at L2
L2 criteria build on L1 and L0. A repository earns L2 by passing ≥ 80% of L2 criteria and meeting the L1 and L0 gates:
DOC-050— Architecture Decision Records folderDOC-060— Runbook / operations documentationDOC-080— Changelog in Keep-a-Changelog formatCQV-050— No forbidden escape hatches in production codeCQV-060— No rawconsole.log/printin production pathsCQV-070— Import ordering enforcedTST-030— Coverage thresholds enforced at ≥ 80%TST-040— End-to-end tests for critical journeysTST-050— Resilient selectors in UI testsBLD-050— Local-setup script or devcontainerOBS-020— Error aggregationOBS-030— Distributed tracingSEC-050— Branch protection onmainSEC-060— DCO or equivalent contribution gatingSEC-070— Dependabot or Renovate configuredTIR-030— Labels defined and documentedDLM-020— Deployment pipeline documentedDLM-030— Deploy previews on PRsDLM-060— Product analytics stubbed
How to climb to L3
The L2 → L3 jump is mostly about documented invariants and review gates. Move
enforcement into CI so nobody can --no-verify their way out, document the
architecture decisions and runbooks, and put the review gates in place that let
a human confidently approve an agent's proposed change. (The published guides
cover the climbs to L1 and L2 — see the guides index; an L2 →
L3 guide is not yet published.)