Prepare the live Sales proof

Make the live lab optional and explicit

The offline exercises explain modelling and missing-evidence refusal without a tenant. A live Sales proof needs additional access, reviewed scope and current execution observations. This lesson prepares that work; reading it authorises no source query, Fabric request or deployment. If the required permissions are unavailable, complete the preparation worksheet and leave live execution unperformed.

Use the current overview's ten-step workflow and owning package guides for executable operations. Do not construct a live command by guessing arguments from the offline scripts. Approved source and Fabric permissions must cover the selected environment, and capacity must support the required items, queries and exports. The historical trial demonstration does not establish your tenant's readiness. PPU alone is insufficient for the documented path.

Agree the source question and grain

Begin with the question the Sales proof will answer. State the meaning of one fact row before selecting a measure. Identify the authorised grain reviewer and preserve the actual ratification decision. The fixture-only decision in the dimensional-model demonstration is not reusable client approval. A source index can describe structure and coverage, but raw extraction and independent oracle capture remain distinct operations.

Review the independent source query separately from the downstream implementation. Explain why it answers the agreed business question and how its coverage and context relate to the required checks. Capture expected values independently and freeze the reviewed catalogue before evaluating the implementation. Do not reuse zero or empty placeholder expectations from the negative regression fixture: those values exist only to test refusal.

Review the consent sequence

Identify source-read scope first. Then distinguish landing or extraction, notebook compilation, Fabric execution, semantic generation, publication, refresh or framing, and report export. These steps can have different effects and data exposure. Review workspace scope, definition bytes and digest-bound plans before the operations that require consent. An earlier installation approval does not approve all later effects.

Compilation alone does not prove that a notebook completed. Definition generation does not prove that the serving model is fresh. A successful query does not prove every rendered state. For each planned step, name the producer result and retained observation needed for the corresponding gate requirement. Keep uncertain external effects visible instead of assuming that repeating a request is harmless.

Plan evidence custody

Actual and expected values, source SQL, DAX and report images can belong in private local evidence. Keep them in customer-controlled custody and out of Academy submissions. Hosted receives a separately exported, signed, value-free projection only under explicit authority. It does not recompute the business comparison. Information supplied to an external assistant is another processing boundary with its own review requirements.

Preparation question	Expected worksheet output
What is being claimed?	Entry boundary, scope and required scenarios
Who owns the meaning?	Grain and oracle review responsibilities
What will execute?	Reviewed actions and exact consent boundaries
What must be retained?	Producer results, receipts and evidence bindings
What remains unobserved?	Tenant prerequisites, render states or pending approvals

Define a stop condition

Stop before live work if access, independent expectations or consent are missing. Stop before claiming qualification if required execution evidence is absent. When a result fails, preserve its diagnostic reason and identify the owning observation or correction. A clean learning narrative is less useful than an honest record that tells the next practitioner what is missing.

Completion check

Produce a synthetic readiness worksheet naming the source question, grain decision, independent expectation route, tenant prerequisites and consent sequence. List the evidence expected at Gold, semantic and report boundaries. Mark actual live operations as unperformed unless you carried them out through the approved workflow. Your plan should explain both the next safe action and why the offline demonstrations cannot substitute for it.