One root cause, one finding Shipped
Cross-cutting concerns have exactly one owning lane, written into the team document rather than left to etiquette — because blind lanes will otherwise all file the same defect.
No reviewer can see who else is on the run, which is what stops a lane from deciding a concern is someone else's problem. The cost is duplication: several blind lanes will independently notice the same concurrency bug. A run on 2026-07-08 filed one blocking-loop issue five times and one path traversal six times, and the duplication buried the unique signal.
Declared ownership
| Concern | Owning lane |
|---|---|
| Concurrency | software-architecture |
| Timeouts | networking-api |
| Failure handling | reliability |
| Missing tests | testing-qa |
| Version hygiene | development-process |
Filing outside your lane is allowed
It is capped at low confidence as a cross-reference rather than forbidden — unless the owning lane is absent from this run, in which case you are the coverage and file at full strength. Forbidding it outright would turn a scope narrowing into a silent coverage hole.