runtime-architecture-review

To check runtime architecture boundaries before applying code changes, review modifications against Application, Run, ExecutionWorker, ExecutionEngine, and Event boundaries to identify affected primitives, detect coupling risks, and propose a minimal safe change shape.

Runtime boundary leak detection identifies product logic embedded in runtime code and evaluates engine coupling risks. You need it when modifying orchestration, transport, workers, or adapters that influence execution flow and workflow loading to prevent subtle regressions.

Review execution flow modifications for tenant isolation risks by evaluating proposed runtime changes against Mozaiks' architecture boundaries, flagging leaks, and assessing operational safeguards related to observability and declarative workflow loading before finalizing the change.

Yes, you can assess code change risk for orchestration and worker adapters without running the full system by providing a concise change summary or relevant file path to evaluate boundary impacts and identify the specific architecture layer affected.

The best way to minimize regressions when updating platform runtime code is to identify affected runtime primitives, detect boundary leaks, and propose the minimal safe change shape using specific file references to respect Application, Run, and ExecutionWorker boundaries.