Skip to content
FDE BI Evidence Workbenchobserved → compared → decided → scoped
AI-authoredscopecurrent

Evidence and access boundary

Current findings are limited to the connected Power BI Desktop model, target findings to the selected workbook, and consultant findings to the supplied source; non-observation is not enterprise-wide absence.

fde-finance.access-boundary · wiki_7c268dbf7f8b78844080cae53f6f0a0e

Senior-authored Markdown

# Boundary

The current snapshot was captured from an open Power BI Desktop model through Modeling MCP. It covers the connected Desktop model only. The target snapshot was declared by `TargetArchitecture_Partial.xlsx`. A separate active consultant source adds upstream observations about journal-control attributes.

## Meaning of “not observed”

When this wiki says an object was not observed, it means it was not returned inside the selected audit and evidence boundary. It does **not** prove that the object or information does not exist in:

- an upstream finance system or governed export;
- another semantic model or PBIX file;
- a dataflow, warehouse, lakehouse or spreadsheet;
- an inaccessible workspace or tenant artefact;
- a later version of the model.

This distinction is demonstrated by `Ledger.JournalSource` and `Ledger.ApprovalStatus`: neither was observed in the selected Desktop model, while a consultant source states that both are available upstream. The consultant evidence supplements but does not rewrite the audit receipt.

The three target gaps are stronger than automated no-match results because recorded consultant decisions confirm the bounded gaps and accept them for phase-two scope. Those decisions still do not prove enterprise-wide absence.

## Areas not established

The available evidence does not establish:

- complete source connection details and M expressions;
- refresh schedules, gateways or deployment environments;
- production row counts, null rates, uniqueness or referential integrity;
- report pages and visual usage;
- production security requirements outside the observed zero-role model;
- exact DAX and production status for the four measures;
- whether the workbook is the complete semantic and non-functional target;
- whether the journal-control attributes are target requirements.

## Revalidation trigger

Revalidate affected pages when broader access, a new current snapshot, an approved source design, a revised target workbook or a journal-control scope decision becomes available.