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

Evidence and access boundary

Current-state findings are limited to the connected Power BI Desktop model, while target findings are limited to the selected workbook; non-observation must not be read as enterprise-wide absence.

fde-finance.access-boundary · wiki_11090e1ee0712c6f5f22212f8b715443

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`.

## 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;
- another semantic model or PBIX file;
- a dataflow, warehouse, lakehouse or spreadsheet;
- an inaccessible workspace or tenant artefact;
- a later version of the model.

The three mapping gaps are stronger than an automated no-match result because a consultant recorded `confirm_gap` decisions. Even so, those decisions concern the selected current evidence and phase-two scope; they do not prove enterprise-wide absence.

## Areas not established

The available evidence does not establish:

- source connection details and complete 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;
- complete DAX expressions and intended production status for the four measures;
- whether the target workbook is the complete non-functional and semantic target.

## Revalidation trigger

Revalidate this wiki when a broader access boundary, a new current snapshot, an approved source design or a revised target artefact becomes available.