widget-exactly-one-source-triple-invariant
Widget data source exclusivity (semantic vs SQL, exactly one) is enforced at three independent layers: Pydantic validator on the schema, a Postgres CHECK constraint in the migration, and a domain error raised at the service layer. Any one layer catching the violation is sufficient; all three together prevent silent data corruption across API, ORM, and raw-SQL paths.
Related
- widget-exactly-one-source-invariant-enforced-three-layers
- 2026-04-04-oracle-001-self-architecture-analysis
- salesforce
- docker
- r-dash-wave-2-pass-1-m4-semantic-m5-governance-models-rls-en
- widget-data-source-invariant-enforced-at-three-layers
- widget-exactly-one-source-invariant-enforced-at-three-layers
- exactly-one-source-invariant-on-widget-requires-three-layer
- triple-layer-invariant-enforcement-pydantic-postgres-service