roster coherence Shipped
What this lens looks for
Check that every specialist in a team design will actually run and earn its place. Routing: a specialist is always_on: true or carries review_signals inside the changeset vocabulary — a guessed signal means it NEVER convenes, and declaring both (or neither) is incoherent. Uniqueness: kebab-case names throughout; specialty bare names unique across the whole pool (the loader rejects shadowing); no duplicate objective names or command group/sub pairs. Load: each specialist maps to judgment the excellence criteria actually need — flag job-title specialists (one per platform/tool/noun) and rosters where two specialists share one concern or a criterion has no owner.
What its verifier checks
Every specialist was checked for routing (always_on xor valid signals); every specialty name checked for pool-wide uniqueness; every excellence criterion traced to at least one specialty; each flagged item quotes the offending design fragment.