widget-data-source-invariant-enforced-at-three-layers
The exactly-one-source invariant on Widget (semantic vs SQL) is enforced at three independent layers: Pydantic validator at request ingress, Postgres CHECK constraint at persistence, and service-layer domain error at business logic. Removing any one layer silently degrades the guarantee — treat all three as required.
Related
- widget-exactly-one-source-invariant-enforced-three-layers
- widget-exactly-one-source-triple-invariant
- 2026-04-04-oracle-001-self-architecture-analysis
- openclaw
- vantage-rbac-rls-non-negotiable-v1-gate
- widget-exactly-one-source-invariant-enforced-at-three-layers
- widget-exactly-one-source-triple-enforcement-pattern
- exactly-one-source-invariant-on-widget-requires-three-layer
- triple-layer-invariant-enforcement-pydantic-postgres-service