kotlin-project-architecture-review

To review Kotlin Multiplatform architecture, evaluate feature proposals and PRs against criteria for layer boundaries, state-holder design, and platform entry-point discipline. This identifies boundary violations and ensures a single source of truth for structure and maintainable design.

Enforcing a single source of truth in KMP involves auditing architectural decisions across modules and layers to ensure clear ownership and proper UI/state boundaries. Applying review criteria to design docs validates structural durability and clean platform boundaries.

Yes, you can use this architecture review to evaluate refactor plans and modularization efforts. It assesses rollout safety, diagnosability, and long-term maintainability guidance for Kotlin Multiplatform projects undergoing structural changes.

You need to audit platform entry-point discipline in KMP when evaluating feature proposals, PR reviews, or refactor efforts across platform boundaries. This ensures proper UI and state separation, maintaining clean architectural ownership and durable design.

A state-holder boundary review works by evaluating architectural decisions to ensure proper UI and state separation within KMP features. It validates layer boundaries and enforces clear ownership, identifying improvement opportunities in design docs or pull requests.