kb-ssot-registries

To prevent configuration drift in a Next.js TypeScript app, model domain data once in a typed registry and wire pre-commit reconcilers and validators into your workflow to block commits if duplicated outputs diverge from the source.

The single source of truth pattern for TypeScript uses a typed `as const` registry to model domain data once, deriving all downstream types and generated platform configs from that single editable file to eliminate duplicated lists.

Yes, you can validate exported handlers without runtime imports by using best-effort static source parsing. This mechanism checks that referenced handlers and exported symbols exist safely during pre-commit validation without executing code.

Set up pre-commit registry validation by configuring a four-phase hook architecture: fix, kit-generic autogen, domain autogen, then validators. Reconcilers silently regenerate derived outputs first, followed by validators to block remaining drift.

You need a registry pattern for cron jobs, navigation, roles, and feature flags when multiple Next.js app consumers access the same domain data. Centralizing this data eliminates duplicated lists and prevents broken integrations across consumers.

Yes, the single source of truth approach works with TypeScript id unions and derived lookup tables by satisfying typed derivation. It automatically derives downstream types and lookup tables directly from the centralized `as const` registry data.