CTR-BI-SEMANTIC · version 3

Reporting Semantic Layer — Reporting measures

Kept in the register rather than deleted, because a superseded contract is a decision and the reasoning is worth keeping.

SupersededNever checked

What the contract says

These are the terms the connector is generated against. A source that stops matching them is a drift finding, not a silent data change.

Entity

Reporting measure · inbound

Primary key

measureKey

Declared volume

1,200 records a day

Freshness commitment

1 d

Owner

N. Ferreira · Data Platform

Vendor

Power BI shared datasets · medium criticality · modeled

Cardinality

One measure to one definition. Definitions are versioned and the platform pins a version rather than tracking latest.

Write-back rule

None.

Review state

Neither review is performed by the team that wrote the contract.

Security reviewApproved

M. Lindqvist · Jul 9, 2026

Privacy reviewApproved

Dr. Katrin Wehner · Jul 28, 2026

Validation and drift

Drift is only detectable on a contract that has been read against a sample.

Last validatedNever

No sample has been read against this contract.

Superseded by the warehouse contract. The semantic layer was going to be the source for reporting measures until it became clear it would put a second definition of the same figure into the platform.

The field list

3 fields · 1 key · 0 personal. The validation rule on each row is what admits or rejects a record at the staging boundary.

Field	Source	Target	Type	Flags	Drift	Validation
Measure key	measure.name	measure.ref	string(80)	keyinternal	Never checked	Unique within the dataset.
Definition	measure.expression	measure.definition	text	internal	Never checked	DAX expression, stored verbatim for audit rather than parsed.
Version	dataset.version	measure.version	string(12)	internal	Never checked	Pinned. Latest is never followed automatically.

What has passed the staging boundary against this contract

1 batch · 310 arrived · 0 admitted · 310 quarantined · 0 rejected

Staging boundary

Batch	Arrived	In	Admitted	Quarantined	Rejected	Result	Gate
STG-0022	Aug 17, 11:00	310	0	310	0	Nothing admitted	No record cleared the gate. 310 are in quarantine and 0 were rejected outright.

Rejects raised against these batches

1 reason covering 310 records. Each one names a field, what was observed and what the contract expected.

Contract superseded, feed accepted only for trace-out310 records · 22 h oldOwner assigned

Observed: A dataset whose contract was superseded 62 days ago

Expected: A ratified contract

STG-0022 · field datasetName · queue quarantine · N. Ferreira

Replay windows

No replay has been requested against this contract.

Replay register

Write-back routes into this system

No write-back route is designed into this system.

Write-back register

What goes stale when this feed does

1 asserted figure depends on Reporting Semantic Layer. The rule on each row is what the surface does when the feed misses its commitment.

Freshness

Figure	Where it is shown	Role	On stale	Note
Traced facts behind unit decisions	Data lineage	contributing	Show it unchanged	The semantic layer explains a fact but is not where the fact comes from. Its contract is superseded and it is being traced out.

What this contract is, and what it is not

A contract, a validation rule, a freshness commitment and a replay path are real mechanisms and they are what this wave builds. What they are not is a connection. No connector on this estate is attached to a customer instance, so every batch, every replay and every write-back attempt recorded here ran against a modeled extract or a sandbox, and the registry keeps saying modeled.

This contract has never been validated against a sample. Every type, every cardinality statement and every validation rule on this page is a declaration taken from documentation, not an observation. Its drift state is unknown rather than clean.