service-integration-architecture

Structure a provider integration using a 4-layer folder layout under packages/integrations. This standard enforces consistent architecture across adapters, separating configuration, webhook handling, and core service logic.

The 4-layer integration model separates provider adapters into distinct layers for configuration, webhook handling, health checks, and core logic. It enforces consistent architecture and secure patterns across all teams in the monorepo.

Implement health checks by registering each provider adapter with a centralized health registry. This monitors integration readiness and enforces CI checks to ensure all services report their health status consistently.

Yes, integration scaffolding requires TypeScript strict mode and Zod-based validation. Zod handles config and payload validation, ensuring type-safe data flows and strict type checking across the 4-layer integration architecture.

Yes, you can enforce CI rules for webhook handling and provider integrations using CI enforcement rules. This ensures new integrations meet the 4-layer standard, register with the health registry, and pass architectural checks before merging.

Use a 4-layer architecture when scaling multiple provider integrations in a monorepo. It standardizes webhook patterns, health registration, and CI enforcement, preventing architectural drift across distributed teams.