Senior-authored Markdown
# Method This build uses two primary evidence artefacts: - the deterministic audit of the connected Power BI Desktop model; - the inspected workbook `TargetArchitecture_Partial.xlsx`. Recorded consultant decision receipts provide authority for mapping confirmation and gap scope. ## Authority classes | Authority | Use in this wiki | |---|---| | `observed` | Returned directly by the audit or exact workbook/evidence read | | `declared` | Stated in the selected target workbook | | `interpreted` | Analytical conclusion derived from evidence | | `decided` | Confirmed by a recorded consultant decision | | `unknown` | Not established inside the selected access boundary | ## Comparison approach The target field list was compared with normalised current-model elements. Exact qualified-name candidates were reviewed and confirmed. Cases without a current candidate descended to bounded evidence packets and were then resolved by consultant decisions. ## Evidence discipline - Existing names and data types support structural comparison, not full semantic equivalence. - A workbook declaration is not an implementation record. - A no-candidate result is bounded non-observation. - A `confirm_gap` decision supports scope treatment but does not prove enterprise-wide absence. - Unknowns remain explicit rather than being inferred away. ## Revalidation A later snapshot, broader estate access, approved source design or revised target workbook should trigger revalidation of affected pages and mappings.