{
  "assessment": "The bounded discovery establishes a reliable field-level baseline but not an implemented target architecture. The connected Power BI Desktop model is a six-table Import model with Account, Calendar, Ledger and Metrics as its business-facing tables, two hidden automatic date tables, four observed measures and three active one-direction relationships. TargetArchitecture_Partial.xlsx declares 13 required columns across Account, Calendar and Ledger. Recorded consultant decisions resolve all 13 mapping cases: ten exact same-qualified-name mappings are approved for reuse_as_is, and Account.AccountGroup, Ledger.CostCentre and Ledger.CurrencyCode are confirmed acquire_or_source gaps accepted for phase-two scope. No partial mapping class is recorded. A separate active consultant source confirms upstream governed-export availability of Ledger.JournalSource and Ledger.ApprovalStatus at ledger-entry grain, but these attributes were not observed in the audited model, are not declared by the selected target workbook and have no mapping or scope decision. The next phase therefore requires governed enrichment design, semantic and data-quality acceptance, a decision on the journal-control attributes, and clarification of broader target requirements for measures, security, refresh and deployment.",
  "edges": [
    {
      "edge_type": "is_explained_by",
      "evidence_artifact_ids": [
        "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
        "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
      ],
      "from_page_id": "fde-finance.access-boundary",
      "note": "The method defines how bounded observations, consultant evidence and unknowns are treated.",
      "reverse_type": "explains",
      "to_page_id": "fde-finance.evidence-method"
    },
    {
      "edge_type": "has_open_questions",
      "evidence_artifact_ids": [
        "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
        "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
      ],
      "from_page_id": "fde-finance.discovery",
      "note": "Unresolved matters requiring client or consultant input.",
      "reverse_type": "questions",
      "to_page_id": "fde-finance.open-questions"
    },
    {
      "edge_type": "highlights_consultant_evidence",
      "evidence_artifact_ids": [
        "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78"
      ],
      "from_page_id": "fde-finance.discovery",
      "note": "Hub navigation to consultant-supplied journal-control evidence and its unresolved scope.",
      "reverse_type": "evidence_highlighted_by",
      "to_page_id": "fde-finance.journal-controls"
    },
    {
      "edge_type": "highlights_gaps",
      "evidence_artifact_ids": [
        "ev_sha256_68cb58d8eb09041ff6f29af5420c9a589b422825a8e96bcd0b721bfd05d5ca4f",
        "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf",
        "ev_sha256_d8f799f9daf1f126be4b2c1972aed8bc3c6d5a24f8b0459e509f1fb55b099904"
      ],
      "from_page_id": "fde-finance.discovery",
      "note": "Hub navigation to the three confirmed target enrichment gaps.",
      "reverse_type": "highlighted_by",
      "to_page_id": "fde-finance.enrichment-gaps"
    },
    {
      "edge_type": "informs_scope",
      "evidence_artifact_ids": [
        "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
        "ev_sha256_68cb58d8eb09041ff6f29af5420c9a589b422825a8e96bcd0b721bfd05d5ca4f",
        "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf",
        "ev_sha256_d8f799f9daf1f126be4b2c1972aed8bc3c6d5a24f8b0459e509f1fb55b099904"
      ],
      "from_page_id": "fde-finance.discovery",
      "note": "Discovery findings inform evidence-supported next-phase work.",
      "reverse_type": "informed_by",
      "to_page_id": "fde-finance.scope-implications"
    },
    {
      "edge_type": "is_bounded_by",
      "evidence_artifact_ids": [
        "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
        "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
      ],
      "from_page_id": "fde-finance.discovery",
      "note": "The engagement conclusion must be read within the selected evidence boundary.",
      "reverse_type": "bounds",
      "to_page_id": "fde-finance.access-boundary"
    },
    {
      "edge_type": "summarises_current_state",
      "evidence_artifact_ids": [
        "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
      ],
      "from_page_id": "fde-finance.discovery",
      "note": "Hub navigation to the bounded observed semantic model.",
      "reverse_type": "summarised_by",
      "to_page_id": "fde-finance.current-model"
    },
    {
      "edge_type": "summarises_decisions",
      "evidence_artifact_ids": [
        "ev_sha256_a5a5cbf21fd0c1e498c04bf7eafbb2c7fa07762ddc368d53d81b7ca82d46db58",
        "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf"
      ],
      "from_page_id": "fde-finance.discovery",
      "note": "Hub navigation to recorded mapping and scope decisions.",
      "reverse_type": "summarised_by",
      "to_page_id": "fde-finance.recorded-decisions"
    },
    {
      "edge_type": "summarises_mapping",
      "evidence_artifact_ids": [
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
        "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
      ],
      "from_page_id": "fde-finance.discovery",
      "note": "Hub navigation to current-to-target mapping results.",
      "reverse_type": "summarised_by",
      "to_page_id": "fde-finance.mapping-coverage"
    },
    {
      "edge_type": "summarises_target_state",
      "evidence_artifact_ids": [
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c"
      ],
      "from_page_id": "fde-finance.discovery",
      "note": "Hub navigation to the workbook-declared target fields.",
      "reverse_type": "summarised_by",
      "to_page_id": "fde-finance.declared-target"
    },
    {
      "edge_type": "uses_method",
      "evidence_artifact_ids": [
        "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
        "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
      ],
      "from_page_id": "fde-finance.discovery",
      "note": "Authority and evidence method for the gold build.",
      "reverse_type": "method_for",
      "to_page_id": "fde-finance.evidence-method"
    },
    {
      "edge_type": "drives_scope",
      "evidence_artifact_ids": [
        "ev_sha256_68cb58d8eb09041ff6f29af5420c9a589b422825a8e96bcd0b721bfd05d5ca4f",
        "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf",
        "ev_sha256_d8f799f9daf1f126be4b2c1972aed8bc3c6d5a24f8b0459e509f1fb55b099904"
      ],
      "from_page_id": "fde-finance.enrichment-gaps",
      "note": "Confirmed enrichment gaps drive supported phase-two work.",
      "reverse_type": "is_driven_by",
      "to_page_id": "fde-finance.scope-implications"
    },
    {
      "edge_type": "raises_questions",
      "evidence_artifact_ids": [
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c"
      ],
      "from_page_id": "fde-finance.enrichment-gaps",
      "note": "Source, ownership and currency questions arise from the target gaps.",
      "reverse_type": "is_raised_by",
      "to_page_id": "fde-finance.open-questions"
    },
    {
      "edge_type": "is_not_declared_by",
      "evidence_artifact_ids": [
        "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c"
      ],
      "from_page_id": "fde-finance.journal-controls",
      "note": "The selected target workbook does not declare the two consultant-supplied journal attributes.",
      "reverse_type": "does_not_declare",
      "to_page_id": "fde-finance.declared-target"
    },
    {
      "edge_type": "raises_questions",
      "evidence_artifact_ids": [
        "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78"
      ],
      "from_page_id": "fde-finance.journal-controls",
      "note": "Journal-control target, source-contract and refresh questions require resolution.",
      "reverse_type": "is_raised_by",
      "to_page_id": "fde-finance.open-questions"
    },
    {
      "edge_type": "requires_scope_decision",
      "evidence_artifact_ids": [
        "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c"
      ],
      "from_page_id": "fde-finance.journal-controls",
      "note": "Upstream availability requires an explicit decision before becoming delivery scope.",
      "reverse_type": "scope_decision_for",
      "to_page_id": "fde-finance.scope-implications"
    },
    {
      "edge_type": "supplements_current_observation",
      "evidence_artifact_ids": [
        "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
        "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
      ],
      "from_page_id": "fde-finance.journal-controls",
      "note": "Consultant evidence adds upstream availability while preserving the audit's bounded non-observation.",
      "reverse_type": "is_supplemented_by",
      "to_page_id": "fde-finance.current-model"
    },
    {
      "edge_type": "contains_gap_detail",
      "evidence_artifact_ids": [
        "ev_sha256_68cb58d8eb09041ff6f29af5420c9a589b422825a8e96bcd0b721bfd05d5ca4f",
        "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf",
        "ev_sha256_d8f799f9daf1f126be4b2c1972aed8bc3c6d5a24f8b0459e509f1fb55b099904"
      ],
      "from_page_id": "fde-finance.mapping-coverage",
      "note": "Three no-candidate target fields are described in detail.",
      "reverse_type": "is_gap_detail_for",
      "to_page_id": "fde-finance.enrichment-gaps"
    },
    {
      "edge_type": "is_confirmed_by",
      "evidence_artifact_ids": [
        "ev_sha256_a5a5cbf21fd0c1e498c04bf7eafbb2c7fa07762ddc368d53d81b7ca82d46db58",
        "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf"
      ],
      "from_page_id": "fde-finance.mapping-coverage",
      "note": "Recorded decisions confirm exact mappings and gap classifications.",
      "reverse_type": "confirms",
      "to_page_id": "fde-finance.recorded-decisions"
    },
    {
      "edge_type": "maps_from",
      "evidence_artifact_ids": [
        "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
      ],
      "from_page_id": "fde-finance.mapping-coverage",
      "note": "Mapping coverage uses observed current columns.",
      "reverse_type": "is_source_for_mapping",
      "to_page_id": "fde-finance.current-model"
    },
    {
      "edge_type": "maps_to",
      "evidence_artifact_ids": [
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c"
      ],
      "from_page_id": "fde-finance.mapping-coverage",
      "note": "Mapping coverage addresses workbook-declared target fields.",
      "reverse_type": "is_target_for_mapping",
      "to_page_id": "fde-finance.declared-target"
    }
  ],
  "pages": [
    {
      "body_markdown": "# Boundary\n\nThe 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.\n\n## Meaning of \u201cnot observed\u201d\n\nWhen 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:\n\n- an upstream finance system or governed export;\n- another semantic model or PBIX file;\n- a dataflow, warehouse, lakehouse or spreadsheet;\n- an inaccessible workspace or tenant artefact;\n- a later version of the model.\n\nThis 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.\n\nThe 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.\n\n## Areas not established\n\nThe available evidence does not establish:\n\n- complete source connection details and M expressions;\n- refresh schedules, gateways or deployment environments;\n- production row counts, null rates, uniqueness or referential integrity;\n- report pages and visual usage;\n- production security requirements outside the observed zero-role model;\n- exact DAX and production status for the four measures;\n- whether the workbook is the complete semantic and non-functional target;\n- whether the journal-control attributes are target requirements.\n\n## Revalidation trigger\n\nRevalidate 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.",
      "claims": [
        {
          "authority": "observed",
          "evidence_artifact_ids": [
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
          ],
          "statement": "The current snapshot covers only the connected Power BI Desktop model accessed through Modeling MCP."
        },
        {
          "authority": "declared",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c"
          ],
          "statement": "The target snapshot is declared by TargetArchitecture_Partial.xlsx."
        },
        {
          "authority": "consultant",
          "evidence_artifact_ids": [
            "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
          ],
          "statement": "The consultant source reports upstream journal-control availability without changing the fact that those attributes were not observed in the audited model."
        },
        {
          "authority": "interpreted",
          "evidence_artifact_ids": [
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
          ],
          "statement": "Non-observation within the selected audit is not proof of absence outside its access boundary."
        },
        {
          "authority": "unknown",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
          ],
          "statement": "Refresh, deployment, broader source, report usage and complete production security requirements are not established."
        }
      ],
      "evidence_artifact_ids": [
        "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
        "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
      ],
      "page_id": "fde-finance.access-boundary",
      "page_type": "scope",
      "status": "current",
      "summary": "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.",
      "title": "Evidence and access boundary"
    },
    {
      "body_markdown": "# Conclusion\n\nThe connected Power BI Desktop model is a small Import semantic model. Its business-facing structure is a ledger star: `Ledger` relates to `Account` and `Calendar`. `Metrics` contains four measures. Two hidden calculated date tables are also present.\n\n## Model inventory\n\n| Table | Observed contents | Storage |\n|---|---|---|\n| `Account` | 3 columns | Import |\n| `Calendar` | 3 columns | Import |\n| `Ledger` | 4 columns | Import |\n| `Metrics` | 1 placeholder column and 4 measures | Import |\n| `DateTableTemplate_4a3e593b-a196-4a2f-9343-f7dc0519ce56` | 7 hidden date columns | Import; calculated partition |\n| `LocalDateTable_88a1fec1-b827-4666-af6e-18472a67bc31` | 7 hidden date columns | Import; calculated partition |\n\nThe audit summary reports six tables, 31 columns, four measures, six partitions, three relationships and zero security roles.\n\n## Business-facing columns\n\n| Table | Column | Data type | Observed metadata |\n|---|---|---|---|\n| `Account` | `AccountKey` | Int64 | Summarise by None |\n| `Account` | `AccountName` | String | Summarise by None |\n| `Account` | `AccountType` | String | Summarise by None |\n| `Calendar` | `DateKey` | Int64 | Summarise by None |\n| `Calendar` | `Date` | DateTime | Format `yyyy-mm-dd`; summarise by None |\n| `Calendar` | `FiscalMonth` | Int64 | Summarise by Sum |\n| `Ledger` | `DateKey` | Int64 | Summarise by None |\n| `Ledger` | `AccountKey` | Int64 | Summarise by None |\n| `Ledger` | `SignedAmount` | Decimal | Format `$#,0.00;($#,0.00)`; summarise by Sum |\n| `Ledger` | `IsAdjustment` | Boolean | Summarise by None |\n| `Metrics` | `Placeholder` | String | Summarise by None |\n\n## Measures\n\nThe following qualified measure names and currency formats were observed:\n\n- `Metrics.Actual Net`\n- `Metrics.Actual Revenue`\n- `Metrics.Budget Net`\n- `Metrics.Net Variance`\n\nThe audit descriptions contain fixture or smoke-test context. That capture context is not promoted here as business meaning. Exact DAX expressions were not returned by the bounded reads used for this build, so production definitions and intended status remain unknown.\n\n## Relationships\n\nAll three observed relationships are active, many-to-one and one-direction:\n\n1. `Ledger.DateKey` \u2192 `Calendar.DateKey`.\n2. `Ledger.AccountKey` \u2192 `Account.AccountKey`.\n3. `Calendar.Date` \u2192 `LocalDateTable_88a1fec1-b827-4666-af6e-18472a67bc31.Date`.\n\nThe third relationship and hidden date tables indicate that automatic date/time behaviour coexists with the explicit `Calendar` table.\n\n## Review observations\n\n- `Calendar.FiscalMonth` is configured to summarise by Sum even though the target declares it as a month number. Summarise by None should be assessed; no change decision is recorded.\n- The intended strategy for the explicit `Calendar` table versus automatic date tables is not recorded.\n- Zero security roles were reported inside this model snapshot. Production security requirements outside the snapshot remain unknown.\n- `Ledger.JournalSource` and `Ledger.ApprovalStatus` were not observed among the four audited `Ledger` columns. A separate consultant source reports upstream availability; it does not alter this audit observation.",
      "claims": [
        {
          "authority": "observed",
          "evidence_artifact_ids": [
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
          ],
          "statement": "The audited model contains six Import tables, 31 columns, four measures, six partitions and three relationships; the audit summary reports zero security roles."
        },
        {
          "authority": "observed",
          "evidence_artifact_ids": [
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
          ],
          "statement": "Ledger relates many-to-one to Calendar through DateKey and to Account through AccountKey, with active one-direction filtering."
        },
        {
          "authority": "interpreted",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
          ],
          "statement": "Calendar.FiscalMonth summarising by Sum is likely inappropriate for a month-number attribute and requires review."
        },
        {
          "authority": "unknown",
          "evidence_artifact_ids": [
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
          ],
          "statement": "Exact DAX definitions and production business semantics for the four Metrics measures are not established by the bounded reads."
        }
      ],
      "evidence_artifact_ids": [
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
        "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
      ],
      "page_id": "fde-finance.current-model",
      "page_type": "current_state",
      "status": "current",
      "summary": "The bounded Desktop audit found a six-table Import model with Account, Calendar, Ledger and Metrics as business-facing tables, two hidden date tables, four measures and three active one-direction relationships.",
      "title": "Observed current semantic model"
    },
    {
      "body_markdown": "# Conclusion\n\n`TargetArchitecture_Partial.xlsx` declares the selected target at field level. The workbook's `Instructions` sheet states that `Target Fields` is the target declaration. The sheet contains 13 rows, all marked `Required = Yes`.\n\n## Declared fields\n\n| Entity | Target field | Type | Business definition | Declared source |\n|---|---|---|---|---|\n| `Account` | `AccountKey` | Int64 | Stable account identifier | Existing Power BI semantic model |\n| `Account` | `AccountName` | String | Finance account display name | Existing Power BI semantic model |\n| `Account` | `AccountType` | String | Revenue or expense classification | Existing Power BI semantic model |\n| `Account` | `AccountGroup` | String | Management reporting group above account type | Account master / embedded mapping |\n| `Calendar` | `DateKey` | Int64 | Integer date key in YYYYMMDD form | Existing Power BI semantic model |\n| `Calendar` | `Date` | DateTime | Posting calendar date | Existing Power BI semantic model |\n| `Calendar` | `FiscalMonth` | Int64 | Fiscal month number | Existing Power BI semantic model |\n| `Ledger` | `DateKey` | Int64 | Posting date foreign key | Existing Power BI semantic model |\n| `Ledger` | `AccountKey` | Int64 | Account foreign key | Existing Power BI semantic model |\n| `Ledger` | `SignedAmount` | Decimal | Signed ledger amount in reporting currency | Existing Power BI semantic model |\n| `Ledger` | `IsAdjustment` | Boolean | Identifies late or manual adjustments | Existing Power BI semantic model |\n| `Ledger` | `CostCentre` | String | Management cost-centre code | Finance posting source / embedded reference data |\n| `Ledger` | `CurrencyCode` | String | ISO reporting currency code | Finance posting source |\n\n## Workbook interpretation boundary\n\nThe workbook contains five sheets: `Instructions`, `Target Fields`, `Mapping Rules`, hidden `Reference Data` and `Validation`. The instructions explicitly prevent treating non-target sheets automatically as target fields.\n\nThe hidden `Reference Data` sheet contains illustrative rows:\n\n| CostCentre | AccountGroup | CurrencyCode |\n|---|---|---|\n| CC100 | Operations | AUD |\n| CC200 | Commercial | AUD |\n| CC300 | Corporate | NZD |\n\nThe workbook does not establish that these values are complete, approved, keyed correctly or governed for production use.\n\n## Attributes not declared by this target\n\n`Ledger.JournalSource` and `Ledger.ApprovalStatus` are described by a separate consultant source, but neither appears in `Target Fields`. Their absence from this workbook is not a decision that they are unnecessary; it means their target status is unresolved.\n\n## Completeness limitation\n\nThe workbook does not declare measures, semantic relationships, security roles, refresh policy, gateway configuration, deployment topology or complete presentation metadata. It is unknown whether those areas are intentionally outside target scope or require further target artefacts.",
      "claims": [
        {
          "authority": "declared",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c"
          ],
          "statement": "The Target Fields sheet declares 13 required columns across Account, Calendar and Ledger."
        },
        {
          "authority": "declared",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c"
          ],
          "statement": "The workbook instructs readers not to treat sheets other than Target Fields automatically as target fields."
        },
        {
          "authority": "observed",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c"
          ],
          "statement": "The hidden Reference Data sheet contains CC100/Operations/AUD, CC200/Commercial/AUD and CC300/Corporate/NZD examples."
        },
        {
          "authority": "unknown",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c"
          ],
          "statement": "Approval, completeness, ownership and join keys for the hidden reference data are not established."
        },
        {
          "authority": "unknown",
          "evidence_artifact_ids": [
            "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c"
          ],
          "statement": "Ledger.JournalSource and Ledger.ApprovalStatus are not declared in the selected Target Fields sheet."
        }
      ],
      "evidence_artifact_ids": [
        "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c"
      ],
      "page_id": "fde-finance.declared-target",
      "page_type": "target_state",
      "status": "current",
      "summary": "TargetArchitecture_Partial.xlsx declares 13 required columns in Account, Calendar and Ledger; it is a field declaration, not evidence of an implemented or complete production architecture.",
      "title": "Declared target fields"
    },
    {
      "body_markdown": "# Engagement state\n\nThe selected evidence supports a bounded current-to-target discovery baseline. It does **not** establish that a target solution has been implemented.\n\nThe connected Power BI Desktop model is an Import semantic model centred on `Ledger`, `Account` and `Calendar`, with a `Metrics` table and two hidden automatic date tables. `TargetArchitecture_Partial.xlsx` declares 13 required target columns across `Account`, `Calendar` and `Ledger`.\n\n## Current-to-target position\n\n| Result | Count | Treatment |\n|---|---:|---|\n| Exact mappings | 10 | Consultant-confirmed `reuse_as_is` |\n| Partial mappings | 0 | No partial or transformed mapping is recorded |\n| Confirmed gaps | 3 | `acquire_or_source`; accepted for phase-two scope |\n\nThe confirmed gaps are:\n\n- `Account.AccountGroup`\n- `Ledger.CostCentre`\n- `Ledger.CurrencyCode`\n\n## Additional consultant evidence\n\nA consultant-supplied source, contributed by **Synthetic Consultant**, states that the governed finance ledger export contains entry-grain `Ledger.JournalSource` and `Ledger.ApprovalStatus` attributes. This is consultant evidence of upstream availability, not MCP observation and not evidence of Power BI implementation. Neither attribute is declared in the selected target workbook or covered by a mapping decision.\n\n## Knowledge map\n\n- **Observed current semantic model** \u2014 tables, columns, measures, partitions and relationships returned by the Desktop audit.\n- **Declared target fields** \u2014 the 13 required columns in the workbook's `Target Fields` sheet.\n- **Current-to-target mapping coverage** \u2014 exact mappings, absence of partial mappings and confirmed gaps.\n- **Required enrichment gaps** \u2014 source and semantic design needed for the three target gaps.\n- **Consultant evidence: journal control attributes** \u2014 upstream availability and unresolved target status of `JournalSource` and `ApprovalStatus`.\n- **Recorded mapping and scope decisions** \u2014 what has been approved and what has not.\n- **Scope implications** \u2014 evidence-supported next-phase work.\n- **Evidence and access boundary** \u2014 what \u201cnot observed\u201d means.\n- **Open discovery questions** \u2014 matters requiring client or consultant resolution.\n- **Evidence and authority method** \u2014 how claims and provenance are handled.\n\n## Overall conclusion\n\nThe declared target is substantially covered at field-structure level, but delivery is not a simple field-addition exercise. The three target enrichments need authoritative sources, keys, governance and acceptance tests. Currency semantics, calendar design and broader architecture requirements remain unresolved. The consultant-supplied journal controls require an explicit target and scope decision before they can be treated as delivery requirements.",
      "claims": [
        {
          "authority": "decided",
          "evidence_artifact_ids": [
            "ev_sha256_22f0ffe13bf533904cdb6581696aec34fb3750db1f7d052d0712e2c5f0eb5afb",
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
            "ev_sha256_68cb58d8eb09041ff6f29af5420c9a589b422825a8e96bcd0b721bfd05d5ca4f",
            "ev_sha256_a5a5cbf21fd0c1e498c04bf7eafbb2c7fa07762ddc368d53d81b7ca82d46db58",
            "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf",
            "ev_sha256_d8f799f9daf1f126be4b2c1972aed8bc3c6d5a24f8b0459e509f1fb55b099904",
            "ev_sha256_f65136ec09176fc91e1f4e63890efd956288c5b1b7665877becd98af942a48e5"
          ],
          "statement": "The selected target declares 13 required columns; recorded consultant decisions approve ten exact reuse mappings and three acquire-or-source gaps."
        },
        {
          "authority": "observed",
          "evidence_artifact_ids": [
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
          ],
          "statement": "The observed current model is a six-table Import model with four measures and three relationships."
        },
        {
          "authority": "consultant",
          "evidence_artifact_ids": [
            "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78"
          ],
          "statement": "A consultant-supplied source states that Ledger.JournalSource and Ledger.ApprovalStatus are available in a governed finance ledger export, but this does not establish their implementation in Power BI."
        },
        {
          "authority": "unknown",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
          ],
          "statement": "No available evidence establishes that the spreadsheet-declared target has been implemented."
        }
      ],
      "evidence_artifact_ids": [
        "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
        "ev_sha256_68cb58d8eb09041ff6f29af5420c9a589b422825a8e96bcd0b721bfd05d5ca4f",
        "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e",
        "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf",
        "ev_sha256_d8f799f9daf1f126be4b2c1972aed8bc3c6d5a24f8b0459e509f1fb55b099904"
      ],
      "page_id": "fde-finance.discovery",
      "page_type": "hub",
      "status": "current",
      "summary": "Ten of 13 workbook-declared target columns have confirmed exact reuse mappings; three required enrichments need sourcing, while consultant-supplied journal controls remain outside the declared target and await a scope decision.",
      "title": "FDE Finance Power BI discovery"
    },
    {
      "body_markdown": "# Conclusion\n\nThree required target columns need acquisition or sourcing. A recorded consultant decision confirms each gap and accepts it for phase-two scope. Here, **gap** means no current candidate was identified inside the audited Desktop model; it does not mean the information is absent from all upstream systems.\n\n## `Account.AccountGroup`\n\n- **Declared definition:** management reporting group above account type.\n- **Type:** String.\n- **Declared source:** account master / embedded mapping.\n- **Comparison:** no selected current candidate.\n- **Decision:** `confirm_gap`; `acquire_or_source`; accepted for phase-two scope.\n\nImplementation needs an authoritative account-level key, classification ownership, effective-dating rules where groups change, and treatment of unmapped accounts.\n\n## `Ledger.CostCentre`\n\n- **Declared definition:** management cost-centre code.\n- **Type:** String.\n- **Declared source:** finance posting source / embedded reference data.\n- **Comparison:** no selected current candidate.\n- **Decision:** `confirm_gap`; `acquire_or_source`; accepted for phase-two scope.\n\nThe source grain remains unresolved. `CostCentre` could be supplied directly per posting or derived through governed reference data; the evidence does not decide between these designs.\n\n## `Ledger.CurrencyCode`\n\n- **Declared definition:** ISO reporting currency code.\n- **Type:** String.\n- **Declared source:** finance posting source.\n- **Comparison:** no selected current candidate.\n- **Decision:** `confirm_gap`; `acquire_or_source`; accepted for phase-two scope.\n\nThe design must be reconciled with `Ledger.SignedAmount`, which the workbook describes as an amount in reporting currency. It is unknown whether the current ledger is single-currency, already converted, or requires transaction and reporting currency separation.\n\n## Reference-data caution\n\nThe hidden workbook sheet contains example values for all three concepts, but the instructions prevent treating that sheet automatically as the target declaration or production source. Completeness, keys, governance and ownership require confirmation.",
      "claims": [
        {
          "authority": "declared",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c"
          ],
          "statement": "Account.AccountGroup is a required String target field declared as a management reporting group sourced from account master or embedded mapping."
        },
        {
          "authority": "declared",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c"
          ],
          "statement": "Ledger.CostCentre is a required String target field declared as a management cost-centre code sourced from the finance posting source or embedded reference data."
        },
        {
          "authority": "declared",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c"
          ],
          "statement": "Ledger.CurrencyCode is a required String target field declared as an ISO reporting currency code sourced from the finance posting source."
        },
        {
          "authority": "decided",
          "evidence_artifact_ids": [
            "ev_sha256_68cb58d8eb09041ff6f29af5420c9a589b422825a8e96bcd0b721bfd05d5ca4f",
            "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf",
            "ev_sha256_d8f799f9daf1f126be4b2c1972aed8bc3c6d5a24f8b0459e509f1fb55b099904"
          ],
          "statement": "All three enrichment gaps were consultant-confirmed and accepted for phase-two scope with action acquire_or_source."
        },
        {
          "authority": "unknown",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
          ],
          "statement": "The authoritative sources, joins, governance and currency treatment for the three enrichments remain unresolved."
        }
      ],
      "evidence_artifact_ids": [
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
        "ev_sha256_68cb58d8eb09041ff6f29af5420c9a589b422825a8e96bcd0b721bfd05d5ca4f",
        "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e",
        "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf",
        "ev_sha256_d8f799f9daf1f126be4b2c1972aed8bc3c6d5a24f8b0459e509f1fb55b099904"
      ],
      "page_id": "fde-finance.enrichment-gaps",
      "page_type": "mapping",
      "status": "current",
      "summary": "Account.AccountGroup, Ledger.CostCentre and Ledger.CurrencyCode have no selected candidate in the bounded current model and require authoritative sourcing under recorded phase-two scope decisions.",
      "title": "Required enrichment gaps"
    },
    {
      "body_markdown": "# Method\n\nThis build uses three evidence paths:\n\n- the deterministic audit of the connected Power BI Desktop model;\n- the inspected workbook `TargetArchitecture_Partial.xlsx`;\n- an active consultant source about journal-control attributes.\n\nRecorded consultant decision receipts provide authority for mapping confirmation and gap scope.\n\n## Authority classes\n\n| Authority | Use in this wiki |\n|---|---|\n| `observed` | Returned directly by the audit or exact workbook/evidence read |\n| `declared` | Stated in the selected target workbook |\n| `interpreted` | Analytical conclusion derived from evidence |\n| `decided` | Confirmed by a recorded consultant or client decision |\n| `consultant` | Evidence explicitly supplied by a named consultant; preserved as consultant provenance |\n| `unknown` | Not established inside the selected access boundary |\n\n## Comparison approach\n\nThe workbook's 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 recorded consultant decisions.\n\nThe journal-control source is separate from that process. It adds upstream knowledge but does not create target rows, mapping cases or decisions and does not rewrite the audit.\n\n## Evidence discipline\n\n- Existing names and data types support structural comparison, not full semantic equivalence.\n- A workbook declaration is not an implementation record.\n- A no-candidate result is bounded non-observation.\n- A `confirm_gap` decision supports scope treatment but does not prove enterprise-wide absence.\n- Consultant evidence is presented with its provenance and is not relabelled as MCP observation.\n- Fixture, synthetic and smoke-test labels are capture context, not business semantics.\n- Unknowns remain explicit rather than being inferred away.\n\n## Revalidation\n\nA later snapshot, broader estate access, approved source design, revised target workbook or recorded journal-control decision should trigger revalidation of affected pages.",
      "claims": [
        {
          "authority": "observed",
          "evidence_artifact_ids": [
            "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
          ],
          "statement": "The current audit, selected target workbook and active consultant source are the evidence paths used for this build."
        },
        {
          "authority": "decided",
          "evidence_artifact_ids": [
            "ev_sha256_68cb58d8eb09041ff6f29af5420c9a589b422825a8e96bcd0b721bfd05d5ca4f",
            "ev_sha256_a5a5cbf21fd0c1e498c04bf7eafbb2c7fa07762ddc368d53d81b7ca82d46db58",
            "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf",
            "ev_sha256_d8f799f9daf1f126be4b2c1972aed8bc3c6d5a24f8b0459e509f1fb55b099904"
          ],
          "statement": "Recorded consultant receipts provide decision authority for exact mappings and confirmed gaps."
        },
        {
          "authority": "consultant",
          "evidence_artifact_ids": [
            "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78"
          ],
          "statement": "The journal-control source is consultant evidence and must not be presented as an audit observation."
        },
        {
          "authority": "interpreted",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
          ],
          "statement": "Structural name and data-type alignment does not by itself establish complete semantic equivalence."
        }
      ],
      "evidence_artifact_ids": [
        "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
        "ev_sha256_68cb58d8eb09041ff6f29af5420c9a589b422825a8e96bcd0b721bfd05d5ca4f",
        "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e",
        "ev_sha256_a5a5cbf21fd0c1e498c04bf7eafbb2c7fa07762ddc368d53d81b7ca82d46db58",
        "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf",
        "ev_sha256_d8f799f9daf1f126be4b2c1972aed8bc3c6d5a24f8b0459e509f1fb55b099904"
      ],
      "page_id": "fde-finance.evidence-method",
      "page_type": "method",
      "status": "current",
      "summary": "The wiki separates audit observations, workbook declarations, analytical interpretations, recorded decisions, consultant evidence and unknowns, with limitations stated beside affected findings.",
      "title": "Evidence and authority method"
    },
    {
      "body_markdown": "# Status\n\nA consultant-supplied source contributed by **Synthetic Consultant** states that a governed finance ledger export contains two entry-grain text attributes:\n\n- `Ledger.JournalSource`\n- `Ledger.ApprovalStatus`\n\nThis is consultant evidence. It is not an MCP audit observation and does not establish implementation in Power BI.\n\n## Consultant-supported interpretation\n\n| Attribute | Consultant description |\n|---|---|\n| `Ledger.JournalSource` | Identifies the originating journal channel, including sub-ledger, recurring, allocation and manual-journal sources |\n| `Ledger.ApprovalStatus` | Records whether a journal is approved, pending or rejected at the time of the finance export |\n\nThe consultant source identifies the **Finance Systems Lead** as the accountable owner. It advises that any implementation should:\n\n- preserve ledger-entry grain;\n- reconcile record counts to the governed extract;\n- document how late approval changes affect refresh behaviour.\n\n## Relationship to the audit\n\nThe audited `Ledger` table contains only:\n\n- `Ledger.DateKey`\n- `Ledger.AccountKey`\n- `Ledger.SignedAmount`\n- `Ledger.IsAdjustment`\n\nTherefore, neither journal-control attribute was observed in the selected current model. The consultant source agrees with that bounded audit result while adding upstream source availability. The two provenance paths are complementary rather than conflicting.\n\n## Relationship to the declared target\n\nNeither attribute appears in the workbook's `Target Fields` sheet. No mapping case or recorded scope decision exists for either attribute. Their target status is therefore unresolved.\n\n## Decision required\n\nThe client and consultant should decide whether these attributes are:\n\n1. required additions to the target and phase-two scope;\n2. future control enhancements outside the selected target; or\n3. supporting source information with no current Power BI requirement.\n\nIf added to scope, the design must confirm the governed export contract, ledger-entry key, refresh cadence, reconciliation control and treatment of late `ApprovalStatus` changes.",
      "claims": [
        {
          "authority": "consultant",
          "evidence_artifact_ids": [
            "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78"
          ],
          "statement": "The consultant-supplied source states that the governed finance ledger export contains entry-grain Ledger.JournalSource and Ledger.ApprovalStatus attributes."
        },
        {
          "authority": "consultant",
          "evidence_artifact_ids": [
            "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78"
          ],
          "statement": "The consultant source identifies the Finance Systems Lead as accountable owner and recommends preserving ledger-entry grain, reconciling record counts and documenting late approval changes."
        },
        {
          "authority": "observed",
          "evidence_artifact_ids": [
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
          ],
          "statement": "Neither Ledger.JournalSource nor Ledger.ApprovalStatus was observed among the four Ledger columns in the selected Desktop audit."
        },
        {
          "authority": "unknown",
          "evidence_artifact_ids": [
            "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c"
          ],
          "statement": "Neither journal-control attribute is declared in the selected Target Fields sheet, and their target and phase-two scope status is unresolved."
        }
      ],
      "evidence_artifact_ids": [
        "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
        "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
      ],
      "page_id": "fde-finance.journal-controls",
      "page_type": "evidence",
      "status": "needs_review",
      "summary": "A consultant source confirms upstream availability of Ledger.JournalSource and Ledger.ApprovalStatus at ledger-entry grain, but neither attribute was observed in the audited model or declared in the selected target.",
      "title": "Consultant evidence: journal control attributes"
    },
    {
      "body_markdown": "# Conclusion\n\nThe selected target is **10 of 13 fields structurally covered** by recorded consultant-confirmed exact mappings. Each covered field maps to a current column with the same qualified name and matching declared and observed data type. The required action is `reuse_as_is`.\n\nNo partial or transformed mapping is recorded. The remaining three cases are confirmed gaps.\n\n## Exact mappings\n\n| Target | Current | Type | Decision |\n|---|---|---|---|\n| `Account.AccountKey` | `Account.AccountKey` | Int64 | Exact; reuse as is |\n| `Account.AccountName` | `Account.AccountName` | String | Exact; reuse as is |\n| `Account.AccountType` | `Account.AccountType` | String | Exact; reuse as is |\n| `Calendar.DateKey` | `Calendar.DateKey` | Int64 | Exact; reuse as is |\n| `Calendar.Date` | `Calendar.Date` | DateTime | Exact; reuse as is |\n| `Calendar.FiscalMonth` | `Calendar.FiscalMonth` | Int64 | Exact; reuse as is |\n| `Ledger.DateKey` | `Ledger.DateKey` | Int64 | Exact; reuse as is |\n| `Ledger.AccountKey` | `Ledger.AccountKey` | Int64 | Exact; reuse as is |\n| `Ledger.SignedAmount` | `Ledger.SignedAmount` | Decimal | Exact; reuse as is |\n| `Ledger.IsAdjustment` | `Ledger.IsAdjustment` | Boolean | Exact; reuse as is |\n\n## Mapping classes\n\n| Mapping class | Count | Finding |\n|---|---:|---|\n| Exact | 10 | Consultant-confirmed |\n| Partial or transformed | 0 | No recorded case |\n| No candidate / gap | 3 | Consultant-confirmed |\n\n## Confirmed gaps\n\n| Target | Bounded comparison result | Required action |\n|---|---|---|\n| `Account.AccountGroup` | No current candidate selected | Acquire or source |\n| `Ledger.CostCentre` | No current candidate selected | Acquire or source |\n| `Ledger.CurrencyCode` | No current candidate selected | Acquire or source |\n\n## What exact mapping proves\n\nThe decisions establish field-level structural reuse. They do not by themselves prove:\n\n- key uniqueness or referential integrity;\n- acceptable null rates and value domains;\n- equivalent business semantics over production data;\n- correct fiscal calendar behaviour;\n- that `Ledger.SignedAmount` has the intended reporting-currency semantics;\n- implementation in a separate target model.\n\n`Ledger.JournalSource` and `Ledger.ApprovalStatus` are outside this mapping result because they are not target rows and have no mapping cases.",
      "claims": [
        {
          "authority": "decided",
          "evidence_artifact_ids": [
            "ev_sha256_1a9901e109d608aac686f20ce58c250b65e77447ba0f60bd2d8e7d13899fdd5f",
            "ev_sha256_22f0ffe13bf533904cdb6581696aec34fb3750db1f7d052d0712e2c5f0eb5afb",
            "ev_sha256_4df30b07fa155491c163d2d2eab2fbb5ac8cda97c270924f9bf205c3370f2e63",
            "ev_sha256_85ce231f68e4b7cce6419c9ceaa82b370be2a48f58e348747ce1b79a16562fc2",
            "ev_sha256_8c8d24e22fc0d23cd4e475c7ba4ddffda702eaa3f5a08527782f5e4d18f7a633",
            "ev_sha256_a5a5cbf21fd0c1e498c04bf7eafbb2c7fa07762ddc368d53d81b7ca82d46db58",
            "ev_sha256_c597fa51292bad547b3638a989999b448915e82791c47875f6e531f30e61fe02",
            "ev_sha256_cff32799405187ec66ad2c061c32a7745cf2169b1ebda4a09b07d851fff36f94",
            "ev_sha256_ec5fbd287517602b0dc45d4064e71280842cb70bfd899c486442f2b2361a7ec0",
            "ev_sha256_f65136ec09176fc91e1f4e63890efd956288c5b1b7665877becd98af942a48e5"
          ],
          "statement": "Ten required target fields have recorded consultant-confirmed exact same-qualified-name mappings with action reuse_as_is."
        },
        {
          "authority": "decided",
          "evidence_artifact_ids": [
            "ev_sha256_68cb58d8eb09041ff6f29af5420c9a589b422825a8e96bcd0b721bfd05d5ca4f",
            "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf",
            "ev_sha256_d8f799f9daf1f126be4b2c1972aed8bc3c6d5a24f8b0459e509f1fb55b099904"
          ],
          "statement": "Account.AccountGroup, Ledger.CostCentre and Ledger.CurrencyCode are recorded consultant-confirmed gap cases with action acquire_or_source."
        },
        {
          "authority": "interpreted",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
            "ev_sha256_68cb58d8eb09041ff6f29af5420c9a589b422825a8e96bcd0b721bfd05d5ca4f",
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e",
            "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf",
            "ev_sha256_d8f799f9daf1f126be4b2c1972aed8bc3c6d5a24f8b0459e509f1fb55b099904"
          ],
          "statement": "The selected mapping result contains exact mappings and no-candidate gaps, with no recorded partial mapping class."
        },
        {
          "authority": "unknown",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
          ],
          "statement": "Production semantic equivalence and data quality for the ten exact mappings have not been established."
        }
      ],
      "evidence_artifact_ids": [
        "ev_sha256_22f0ffe13bf533904cdb6581696aec34fb3750db1f7d052d0712e2c5f0eb5afb",
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
        "ev_sha256_68cb58d8eb09041ff6f29af5420c9a589b422825a8e96bcd0b721bfd05d5ca4f",
        "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e",
        "ev_sha256_a5a5cbf21fd0c1e498c04bf7eafbb2c7fa07762ddc368d53d81b7ca82d46db58",
        "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf",
        "ev_sha256_d8f799f9daf1f126be4b2c1972aed8bc3c6d5a24f8b0459e509f1fb55b099904",
        "ev_sha256_f65136ec09176fc91e1f4e63890efd956288c5b1b7665877becd98af942a48e5"
      ],
      "page_id": "fde-finance.mapping-coverage",
      "page_type": "mapping",
      "status": "current",
      "summary": "Ten target columns have confirmed exact mappings to current columns; no partial mapping is recorded; three required target columns have no selected current candidate and are confirmed gaps.",
      "title": "Current-to-target mapping coverage"
    },
    {
      "body_markdown": "# Priority questions\n\n## Journal controls\n\n1. Should `Ledger.JournalSource` and `Ledger.ApprovalStatus` be added to the target and phase-two scope, retained as future enhancements, or excluded from the current Power BI requirement?\n2. Can the Finance Systems Lead confirm the governed export identifier, extraction contract, refresh cadence and approved access path?\n3. What ledger-entry key will preserve grain and support record-count reconciliation?\n4. How should late `ApprovalStatus` changes be represented: current-state overwrite, effective dating, snapshot history or another governed method?\n\n## Enrichment and ownership\n\n5. Are the hidden `Reference Data` values governed mappings or illustrative workbook content?\n6. Which authoritative systems or governed datasets supply `Account.AccountGroup`, `Ledger.CostCentre` and `Ledger.CurrencyCode`?\n7. What key joins `AccountGroup` to `Account`, and at what grain are `CostCentre` and `CurrencyCode` joined to `Ledger`?\n8. Who owns data quality, unmapped values, effective dating and change approval for each enrichment?\n\n## Currency semantics\n\n9. Does `Ledger.SignedAmount` represent transaction currency, reporting currency or an already converted single-currency amount?\n10. Is `Ledger.CurrencyCode` intended to describe transaction currency, reporting currency or both?\n11. If conversion is required, where are exchange rates, rate types and conversion dates governed?\n\n## Calendar and model design\n\n12. Should `Calendar.FiscalMonth` use summarise by None?\n13. Are fiscal year, fiscal quarter, sort columns and marked-date-table requirements missing from the partial workbook?\n14. Should automatic date/time and the hidden local date tables be removed in favour of the explicit `Calendar` table?\n\n## Measures and business semantics\n\n15. What are the exact DAX expressions and intended production status of `Metrics.Actual Net`, `Metrics.Actual Revenue`, `Metrics.Budget Net` and `Metrics.Net Variance`?\n16. Are measures intentionally outside the target workbook, or is another target artefact required?\n\n## Security, operations and acceptance\n\n17. Are row-level or object-level security requirements expected in production despite zero roles in the observed model?\n18. What source connections, M logic, refresh behaviour, gateways, environments and deployment controls apply?\n19. Is `TargetArchitecture_Partial.xlsx` intentionally limited to fields, or should the target also define relationships, measures, security, refresh and presentation metadata?\n20. What tests will prove the ten `reuse_as_is` mappings are semantically correct, including uniqueness, referential integrity, nullability, domains and currency behaviour?",
      "claims": [
        {
          "authority": "unknown",
          "evidence_artifact_ids": [
            "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c"
          ],
          "statement": "Target and phase-two scope treatment for Ledger.JournalSource and Ledger.ApprovalStatus is unresolved."
        },
        {
          "authority": "unknown",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c"
          ],
          "statement": "Approval and production use of the workbook's hidden reference data are unresolved."
        },
        {
          "authority": "unknown",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
          ],
          "statement": "Currency semantics for Ledger.SignedAmount and Ledger.CurrencyCode are unresolved."
        },
        {
          "authority": "unknown",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
          ],
          "statement": "Production requirements for measures, security, refresh, deployment and target completeness are unresolved."
        }
      ],
      "evidence_artifact_ids": [
        "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
        "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
      ],
      "page_id": "fde-finance.open-questions",
      "page_type": "question",
      "status": "needs_review",
      "summary": "Client and consultant input is required on journal-control scope, enrichment sources, currency semantics, calendar design, measure status, security, operations and acceptance testing.",
      "title": "Open discovery questions"
    },
    {
      "body_markdown": "# Decision status\n\nAll 13 selected mapping cases are resolved by recorded consultant decisions.\n\n## Reuse decisions\n\nThe following targets are confirmed as exact mappings with required action `reuse_as_is`:\n\n- `Account.AccountKey`\n- `Account.AccountName`\n- `Account.AccountType`\n- `Calendar.DateKey`\n- `Calendar.Date`\n- `Calendar.FiscalMonth`\n- `Ledger.DateKey`\n- `Ledger.AccountKey`\n- `Ledger.SignedAmount`\n- `Ledger.IsAdjustment`\n\nThese decisions confirm deterministic field mappings. They do not waive semantic or data-quality acceptance testing.\n\n## Gap and scope decisions\n\nThe following targets are confirmed gaps with action `acquire_or_source` and scope state `accepted_for_scope`:\n\n- `Account.AccountGroup`\n- `Ledger.CostCentre`\n- `Ledger.CurrencyCode`\n\nThe recorded reasons state that no current evidence was available and the gaps were accepted for phase-two scope.\n\n## No recorded decision\n\nThere is no mapping or scope decision for:\n\n- `Ledger.JournalSource`\n- `Ledger.ApprovalStatus`\n\nTheir upstream availability comes from consultant evidence, not from the mapping decision set.\n\n## Decision boundary\n\nThe recorded decisions do not establish:\n\n- upstream source design;\n- transformation, join or effective-dating logic;\n- implementation completion;\n- production acceptance;\n- broader target requirements outside the workbook's field list.",
      "claims": [
        {
          "authority": "decided",
          "evidence_artifact_ids": [
            "ev_sha256_1a9901e109d608aac686f20ce58c250b65e77447ba0f60bd2d8e7d13899fdd5f",
            "ev_sha256_22f0ffe13bf533904cdb6581696aec34fb3750db1f7d052d0712e2c5f0eb5afb",
            "ev_sha256_4df30b07fa155491c163d2d2eab2fbb5ac8cda97c270924f9bf205c3370f2e63",
            "ev_sha256_85ce231f68e4b7cce6419c9ceaa82b370be2a48f58e348747ce1b79a16562fc2",
            "ev_sha256_8c8d24e22fc0d23cd4e475c7ba4ddffda702eaa3f5a08527782f5e4d18f7a633",
            "ev_sha256_a5a5cbf21fd0c1e498c04bf7eafbb2c7fa07762ddc368d53d81b7ca82d46db58",
            "ev_sha256_c597fa51292bad547b3638a989999b448915e82791c47875f6e531f30e61fe02",
            "ev_sha256_cff32799405187ec66ad2c061c32a7745cf2169b1ebda4a09b07d851fff36f94",
            "ev_sha256_ec5fbd287517602b0dc45d4064e71280842cb70bfd899c486442f2b2361a7ec0",
            "ev_sha256_f65136ec09176fc91e1f4e63890efd956288c5b1b7665877becd98af942a48e5"
          ],
          "statement": "Recorded consultant decisions confirm exact reuse for ten target fields."
        },
        {
          "authority": "decided",
          "evidence_artifact_ids": [
            "ev_sha256_68cb58d8eb09041ff6f29af5420c9a589b422825a8e96bcd0b721bfd05d5ca4f",
            "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf",
            "ev_sha256_d8f799f9daf1f126be4b2c1972aed8bc3c6d5a24f8b0459e509f1fb55b099904"
          ],
          "statement": "Recorded consultant decisions confirm three acquire-or-source gaps and accept them for phase-two scope."
        },
        {
          "authority": "unknown",
          "evidence_artifact_ids": [
            "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c"
          ],
          "statement": "No mapping or scope decision for Ledger.JournalSource or Ledger.ApprovalStatus is established by the available decision evidence."
        },
        {
          "authority": "unknown",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
            "ev_sha256_68cb58d8eb09041ff6f29af5420c9a589b422825a8e96bcd0b721bfd05d5ca4f",
            "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf",
            "ev_sha256_d8f799f9daf1f126be4b2c1972aed8bc3c6d5a24f8b0459e509f1fb55b099904"
          ],
          "statement": "The decisions do not establish source design, implementation completion or production acceptance."
        }
      ],
      "evidence_artifact_ids": [
        "ev_sha256_22f0ffe13bf533904cdb6581696aec34fb3750db1f7d052d0712e2c5f0eb5afb",
        "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
        "ev_sha256_68cb58d8eb09041ff6f29af5420c9a589b422825a8e96bcd0b721bfd05d5ca4f",
        "ev_sha256_a5a5cbf21fd0c1e498c04bf7eafbb2c7fa07762ddc368d53d81b7ca82d46db58",
        "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf",
        "ev_sha256_d8f799f9daf1f126be4b2c1972aed8bc3c6d5a24f8b0459e509f1fb55b099904",
        "ev_sha256_f65136ec09176fc91e1f4e63890efd956288c5b1b7665877becd98af942a48e5"
      ],
      "page_id": "fde-finance.recorded-decisions",
      "page_type": "decision",
      "status": "current",
      "summary": "Recorded consultant decisions authorise reuse of ten exact current fields and place three confirmed target enrichments into phase-two scope; no decision covers the journal-control attributes.",
      "title": "Recorded mapping and scope decisions"
    },
    {
      "body_markdown": "# Conclusion\n\nThe evidence supports a focused next phase, but not a field-addition-only implementation. The three confirmed enrichment gaps require source and semantic design, and the ten exact mappings require validation against production expectations.\n\n## Supported phase-two work\n\n1. **Source `Account.AccountGroup`.** Confirm the account master or governed mapping, join key, hierarchy rules, effective dating and ownership.\n2. **Source `Ledger.CostCentre`.** Decide whether it is supplied at posting grain or derived through governed reference data; define unmatched-value handling.\n3. **Source `Ledger.CurrencyCode`.** Establish transaction and reporting currency semantics and reconcile them with `Ledger.SignedAmount`.\n4. **Validate reuse mappings.** Test uniqueness, referential integrity, nullability, value domains and representative business results.\n5. **Resolve calendar design.** Review `Calendar.FiscalMonth` summarisation, fiscal sorting and the coexistence of explicit and automatic date tables.\n\n## Journal-control scope decision\n\nConsultant evidence confirms upstream availability of `Ledger.JournalSource` and `Ledger.ApprovalStatus`, but the selected target and decisions do not place them in scope. Before implementation planning, decide whether they are required target attributes.\n\nIf accepted into scope, evidence supports these design controls:\n\n- preserve ledger-entry grain;\n- confirm the governed export and entry key;\n- reconcile record counts to the extract;\n- document treatment of late `ApprovalStatus` changes;\n- retain the Finance Systems Lead's ownership role unless superseded by a recorded decision.\n\n## Scope not yet justified as complete\n\nConfirm whether the target also requires:\n\n- production measures and KPI definitions;\n- relationships and date-table designation;\n- row-level or object-level security;\n- refresh policy, incremental refresh and gateway configuration;\n- deployment environments and release controls;\n- report presentation requirements;\n- data-quality monitoring and operational ownership.\n\n## Delivery caution\n\nThe hidden workbook reference data is discovery evidence, not an approved production source. It should not be promoted into delivery design without explicit confirmation.",
      "claims": [
        {
          "authority": "decided",
          "evidence_artifact_ids": [
            "ev_sha256_68cb58d8eb09041ff6f29af5420c9a589b422825a8e96bcd0b721bfd05d5ca4f",
            "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf",
            "ev_sha256_d8f799f9daf1f126be4b2c1972aed8bc3c6d5a24f8b0459e509f1fb55b099904"
          ],
          "statement": "The three confirmed gaps support phase-two acquisition or sourcing work."
        },
        {
          "authority": "interpreted",
          "evidence_artifact_ids": [
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
          ],
          "statement": "Source design, semantic validation and ownership are necessary implications of the declared enrichments and current evidence gaps."
        },
        {
          "authority": "consultant",
          "evidence_artifact_ids": [
            "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78"
          ],
          "statement": "The consultant source supports ledger-entry grain preservation, extract record-count reconciliation and treatment of late approval changes if the journal controls are implemented."
        },
        {
          "authority": "unknown",
          "evidence_artifact_ids": [
            "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
            "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
            "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e"
          ],
          "statement": "The selected evidence does not establish complete scope for journal controls, security, refresh, deployment, measures or report presentation."
        }
      ],
      "evidence_artifact_ids": [
        "ev_sha256_388c689a963f313c709060d18bf37954425b7060a7ac0a5d541be0c51c738a78",
        "ev_sha256_480433cbc86b45db9ec61c5c174d60618afe10338cbd09c31c5a523ee7f33e5c",
        "ev_sha256_68cb58d8eb09041ff6f29af5420c9a589b422825a8e96bcd0b721bfd05d5ca4f",
        "ev_sha256_a11f31dfefa7810703c3ae3ff271a0b73fcebc2086787da89d17b58544c43d6e",
        "ev_sha256_c406e2ec60e09e96387ed519d698dca13575de450153a59b9e642933e6470ccf",
        "ev_sha256_d8f799f9daf1f126be4b2c1972aed8bc3c6d5a24f8b0459e509f1fb55b099904"
      ],
      "page_id": "fde-finance.scope-implications",
      "page_type": "scope",
      "status": "current",
      "summary": "Phase two is supported for the three governed enrichments and reuse validation; the journal controls and broader architecture requirements require explicit scope decisions.",
      "title": "Scope implications"
    }
  ],
  "review_flags": [
    {
      "priority": 10,
      "queue_name": "client_question",
      "reason": "Confirm authoritative sources, keys, ownership, effective dating and unmatched-value handling for Account.AccountGroup, Ledger.CostCentre and Ledger.CurrencyCode.",
      "subject_id": "fde-finance.enrichment-gaps",
      "subject_type": "page"
    },
    {
      "priority": 15,
      "queue_name": "client_question",
      "reason": "Resolve currency semantics for Ledger.SignedAmount and Ledger.CurrencyCode, including transaction versus reporting currency and any conversion design.",
      "subject_id": "fde-finance.open-questions",
      "subject_type": "page"
    },
    {
      "priority": 30,
      "queue_name": "consultant_review",
      "reason": "Review Calendar.FiscalMonth summarisation and the explicit Calendar versus automatic date/time strategy.",
      "subject_id": "fde-finance.current-model",
      "subject_type": "page"
    },
    {
      "priority": 5,
      "queue_name": "consultant_review",
      "reason": "Finance Systems Lead or authorised consultant should confirm the governed export contract, ledger-entry key, refresh cadence, reconciliation control and late ApprovalStatus treatment.",
      "subject_id": "fde-finance.journal-controls",
      "subject_type": "page"
    },
    {
      "priority": 35,
      "queue_name": "evidence_research",
      "reason": "Obtain exact DAX expressions and approved business definitions for the four Metrics measures.",
      "subject_id": "fde-finance.current-model",
      "subject_type": "page"
    },
    {
      "priority": 20,
      "queue_name": "evidence_research",
      "reason": "Obtain source specifications and representative data evidence for the three acquire-or-source target fields.",
      "subject_id": "fde-finance.enrichment-gaps",
      "subject_type": "page"
    },
    {
      "priority": 100,
      "queue_name": "revalidation",
      "reason": "Revalidate affected findings when a broader estate audit, revised target workbook, approved source design or journal-control decision becomes available.",
      "subject_id": "fde-finance.access-boundary",
      "subject_type": "page"
    },
    {
      "priority": 40,
      "queue_name": "revalidation",
      "reason": "Revalidate the ten reuse_as_is mappings against production data for uniqueness, referential integrity, nullability, domains and semantic equivalence.",
      "subject_id": "fde-finance.mapping-coverage",
      "subject_type": "page"
    },
    {
      "priority": 25,
      "queue_name": "scope",
      "reason": "Confirm whether measures, relationships, security, refresh, gateways, deployment and presentation metadata require additional target artefacts.",
      "subject_id": "fde-finance.declared-target",
      "subject_type": "page"
    },
    {
      "priority": 1,
      "queue_name": "scope",
      "reason": "Decide whether Ledger.JournalSource and Ledger.ApprovalStatus become target fields and phase-two delivery scope; upstream availability alone is not a scope decision.",
      "subject_id": "fde-finance.journal-controls",
      "subject_type": "page"
    }
  ],
  "review_note": "Complete replacement gold build for the selected current and target snapshots. The build preserves the distinction between MCP observations, workbook declarations, recorded decisions, consultant-supplied evidence and unknowns. It adds a dedicated journal-control evidence page so the active consultant source is represented without rewriting the immutable audit observation. Open matters are queued for client, consultant, scope and revalidation review."
}