opl-source-module-boundary-reviewer

To check for OPL source module boundary violations, audit new source code contributions against OPL modular architecture standards by detecting incorrect module placement, invalid dependency directions, and forbidden deep imports before merging.

A source module boundary review in OPL architecture is a compliance audit that inspects module ownership claims, import maps, and dependency direction to prevent modularity breakdowns and architecture rule breaks.

Classify deep import and dependency direction issues by categorizing detected violations as wrong owner module, deep import, forbidden dependency, public entrypoint gap, or ambiguous module boundary during the architecture compliance audit.

Yes, pre-merge validation for forbidden deep imports provides minimal correction recommendations for boundary violations while strictly avoiding unauthorized source mutations or readiness claims.

You need to run a module boundary audit for OPL contributions during code review workflows for new source modules to ensure source changes adhere to modular architecture standards and catch technical debt early.