kb-ssot-registries

What problem does it solve?

It prevents drift and broken integrations when multiple parts of a Next.js app consume the same domain data by centralizing that data into a single editable registry.

Core Features & Use Cases

• Portable registry-as-SSOT: Model a domain once (as a typed as const registry) and derive all downstream types/configs from it.
• Reconcile vs validate guardrails: Use pre-commit reconcilers to regenerate derived outputs silently, and validators to block commits when drift still exists or hooks are bypassed.
• Best-effort handler resolution: Validate that referenced handlers/exported symbols exist using static source parsing instead of runtime imports.
• Four-phase pre-commit workflow: Fit registry derivation and validation into a predictable hook architecture (fix, kit-generic autogen, domain autogen, then validators).

Quick Start

Use the kb-ssot-registries pattern to replace duplicated domain lists (for example, roles, navigation items, or notification categories) with a single editable registry file and wire its reconciler and validator into your pre-commit flow.