Governance boundaries

CRISP treats meaning as a programme asset with owners and release trains. Rules catalogues are inspectable. Identity exceptions are first-class. KPIs are named in Publish. Pipelines execute; they do not quietly author truth.

Who authors meaning

Rules

SP_CORE_CONFORM_RULE

Enums · maps · sign

Identity

Exceptions + hubs

Cross-source sameness

Publish

SP_CORE_PUBLISH

KPI / measure contracts

read-only contract

Consumers

BI · API · reports — forbid redefine(measure) in calc fields / semantic layers

Pipelines execute; programme assets author meaning. Consumers read Publish — they do not redefine KPIs or sameness.

What are the governance pillars?

Pillars

Release-controlled rules — maps, sign, lifecycle passes versioned in SP_CORE_CONFORM_RULE, not buried in developer SQL across dozens of marts.
Auditable to the source — Conform preserves native keys and tritemporal intervals; Span/Publish replay contracts answer close-day questions.
Authoritative sameness — Identity decides which records are the same subject; dashboards do not.
Publish owns KPIs — GWP, revenue, consolidation lines are programme contracts. BI consumes; it does not invent.

Governance invariants

# Who may change enterprise tokens?
assert rule_changes require programme_release
assert identity_exceptions are modelled rows   # not emails

# Where may KPIs be defined?
assert measure_definitions ⊆ SP_CORE_PUBLISH
forbid redefine(measure) in tableau_calc_fields
forbid redefine(measure) in semantic_layer_yaml

# What may consumers read?
assert consumer_sql.targets ⊆ SP_CORE_PUBLISH

Back to homepage Revisit Publish