01 How it works
From source.
To signed proof.
Six deliberate steps connect the business question to the report and its evidence. Each handoff has a scope. Each decision has an owner.
02 Source intelligence
Map the source.
Agree the question.
Start with explicit read consent. Profile SQL Server or PostgreSQL into a value-free source index: structure, keys, types and declared coverage.
Author oracle queries and expected values independently. Review their business meaning before freezing the required scenarios. Source profiling, raw extraction and oracle capture are distinct operations.
Human decision · read consent + business question03 Dimensional design
Settle what one row means.
Connect the business process to a dimensional design. Before Gold compilation, a person confirms the fact grain: the precise business event or snapshot that one row represents.
Sales, Accounts Payable, Accounts Receivable, General Ledger and Inventory seeds are draft starting points. They help structure the discussion; your business definition still needs ratification.
Human decision · grain ratification04 Customer-controlled execution
Build inside your Fabric environment.
Compile batch-bound Bronze, Silver and Gold notebooks with a reviewed execution plan. The execution boundary enforces workspace scope, consent and definition digests.
Compilation produces artifacts. Live execution needs its own observations. Incremental capture and history paths are in preview, with separate contracts and scope-specific evidence requirements.
Human decision · execution consent05 Serve and report
Give the model a clear expression.
Generate the semantic model. Probe DAX against independent expectations before committing measures. Produce PBIR pages with model-resolved fields and deterministic geometry.
Deploy through a digest-bound plan, read definitions back, refresh and frame the model as required. Then capture actual queries and report exports. A successful authoring operation does not establish numerical correctness.
06 Independent qualification
Check the claim.
Keep its limits visible.
Producers emit step results; only the ledger records receipts. Gates recompute numeric comparisons against frozen expectations, inspect current evidence and propagate staleness.
History qualification also binds source, run, coverage and expectation epochs, batch identity and receipt selections. Separate report-state and Windows OCR checks are in preview: they compare bounded visible labels with independent display expectations.
Missing, clipped or contradictory evidence cannot pass. Business interpretation and visual acceptance remain people's decisions.
Human decision · business + visual acceptance08 Read the scope
What qualification does
and does not mean.
A green result is useful when you can explain exactly what was checked, against which expectation, and when.
What it establishes
- Declared checks passed against independently established expectations.
- Named scope and observations are bound to the retained, current evidence.
- Changes can make proof stale. Dependencies and newer failed retries matter.
What stays with you
- Business acceptance. Grain, interpretation and visual acceptance require people.
- Untested states. A pass does not cover every value, security context or future refresh.
- The underlying numbers. Hosted verifies signed metadata; it does not recalculate source truth.