platform-design-principles

Apply clean architecture principles by separating core domain logic from infrastructure using ports and adapters, centralizing variant data as a single source of truth, and generating cross-boundary contracts to reduce manual type sync.

Ports and adapters is an architectural pattern that enforces separation of core domain logic from infrastructure by guiding teams to define interfaces and implement adapters for external system boundaries.

Maintain a single source of truth by centralizing the definition of variant data like roles and statuses, which prevents duplication across codebases and ensures consistency throughout the software project.

The best way to generate cross-boundary contracts is to derive them from a single centralized source, which reduces manual type synchronization and prevents duplicated effort across module boundaries.

No, you do not need additional tooling to enforce platform design principles; the guidance focuses on ports, adapters, single source of truth, and generated contracts during module design and interface definition.

Review system architecture decisions when creating new modules, defining service interfaces, or discussing system boundaries to prevent tightly coupled code and duplicated effort in maintainable systems.