widget-exactly-one-source-triple-enforcement-pattern
The exactly-one-source invariant on Widget (either Cube semantic query OR SQL cache path, never both, never neither) is enforced at three layers simultaneously: Pydantic validator (request-time), Postgres CHECK constraint (DB-time), and service-layer domain error (business logic). This triple-layer pattern prevents the invariant from being bypassed at any entry point.
Related
- widget-exactly-one-source-invariant-enforced-at-three-layers
- widget-exactly-one-source-invariant-enforced-three-layers
- widget-data-source-invariant-enforced-at-three-layers
- snowflake
- 2026-04-04-oracle-001-self-architecture-analysis
- exactly-one-source-invariant-on-widget-requires-three-layer
- triple-layer-invariant-enforcement-pydantic-postgres-service