Senior-authored Markdown
# Status The selected evidence supports a bounded current-to-target discovery baseline. The observed Power BI Desktop model is an Import semantic model centred on `Ledger`, `Account` and `Calendar`. The selected workbook, `TargetArchitecture_Partial.xlsx`, declares 13 required target columns across those three entities. Consultant decisions confirm: - **10 exact mappings** with action `reuse_as_is`; - **3 required gaps** with action `acquire_or_source`; - the three gaps are accepted for **phase-two scope**. This is not evidence that a target solution has been implemented. ## Knowledge map - **Observed current model** — tables, columns, measures, partitions and relationships found in the connected Desktop model. - **Declared target** — the 13 columns declared by the workbook's `Target Fields` sheet. - **Mapping coverage** — exact mappings and comparison result. - **Enrichment gaps** — `Account.AccountGroup`, `Ledger.CostCentre` and `Ledger.CurrencyCode`. - **Recorded decisions** — reuse and phase-two scope decisions. - **Access boundary** — what the evidence can and cannot establish. - **Open questions** — client and consultant matters still requiring resolution. - **Evidence method** — authority classes and evidence handling used in this wiki. ## Overall position The current model structurally covers the core account, date and ledger fields declared by the target. The unresolved work is concentrated in management reporting enrichment, currency semantics, source ownership and broader non-field architecture requirements such as security, refresh and deployment. The workbook is explicitly partial in effect: it declares fields, but does not establish implementation of measures, relationships, security, refresh policy or deployment architecture.