aim-shared-domain

To enforce shared Go package boundaries, you define allowed and forbidden dependencies for your shared modules, ensuring business services like auth and gateway can reuse cross-cutting types without creating reverse dependencies that cause service-level coupling.

Propagating tracing context in Kafka events requires injecting span and trace data directly into event payloads using shared tracing utilities. This ensures distributed tracing continuity across module boundaries when processing Kafka-driven event flows.

Integrating a Nacos gRPC resolver requires using the specified gRPC/Nacos resolver scheme within the shared package scope. You must follow package isolation constraints to keep the resolver integration consistent across client modules without introducing reverse dependencies.

Adding a new shared package to app/shared requires extracting and adhering to specific modification checks for dependency rules. You must verify that the new package maintains package isolation constraints and does not introduce reverse dependencies from business services.

Unified error conversion across Go module boundaries is handled by using shared errorx domains within the shared package scope. This ensures consistent error handling and schema validation when flows cross between auth, core, gateway, and logic modules.

You should not use a shared package approach when the functionality introduces reverse dependencies from business services into shared modules. If the logic cannot adhere to package isolation constraints and tracing propagation contracts, it belongs in the service module instead.