Start here

Overview Shipped

A scope decides which specialists are eligible before any of them run. It is the cheapest stage in the pipeline and the one that most changes what the report looks like.

A review with every lens on is a review nobody finishes reading. A scope answers one question — which specialists are even eligible — and it answers it before a single model is dispatched, so an excluded lens costs nothing at all. devteam defines 19.

Why the default is not "everything"

risk is the default: 14 of 23 specialists, chosen because their absence is what lets a real defect through. Completeness — accessibility, localization, the platform lenses — is opt-in rather than on, because a report that flags a missing RTL layout beside a data-loss bug has buried the data-loss bug.

Specialists convened, by scope

  • risk14default
  • conformance7
  • completeness6
  • performance6
  • platform-native5
  • reliability5
  • accessibility3
  • api3
  • architecture3
  • code-quality3
  • security3
  • i18n2
  • observability2
  • ui-ux2
  • claude-code1
  • data1
  • recipe1
  • safety1
  • testing1

Every scope but the default is a deliberate narrowing. The long tail on the right is the point: a single-lens scope is a legitimate way to run this.