T-U72C-generic-ops-registry-composition-path

Status: closed/done · Impact: medium · Complexity: small

Goal

The op registry’s discovery walk roots only entities/<type>/ops/ and services/<service>/ops/, so generic cross-entity ops under model/ops/ cannot self-register via the walk; they instead register through explicit defineOp at import via a barrel. Either D-0007 §2a (and/or the registry doc) should state which composition path generic cross-entity ops use, or the module-walk should gain a model/ops/ discovery root — so the registration story for generic ops is no longer a side-channel an implementer has to rediscover.

The op registry’s discovery walk roots only entities/<type>/ops/ and services/<service>/ops/, so generic cross-entity ops under model/ops/ cannot self-register via the walk and instead register through explicit defineOp at import via a barrel. D-0007 §2a (and/or the registry doc) should state which composition path generic cross-entity ops use, or the module-walk should gain a model/ops/ discovery root. Surfaced by T-0010’s relocation of audit/validate/migrate/check-identifiers into model/ops/.

— from T-0010 post-mortem (Friction and automation gaps)