AI-authoreddecisioncurrent

Recorded mapping and scope decisions

Consultant decisions authorise reuse of ten exact current fields and place three confirmed enrichment gaps into phase-two scope; they do not constitute implementation approval.

fde-finance.recorded-decisions · wiki_11090e1ee0712c6f5f22212f8b715443

Senior-authored Markdown

# Decision status

All 13 selected mapping cases are resolved by recorded consultant decisions.

## Reuse decisions

The following targets are confirmed as exact mappings with required action `reuse_as_is`:

- `Account.AccountKey`
- `Account.AccountName`
- `Account.AccountType`
- `Calendar.DateKey`
- `Calendar.Date`
- `Calendar.FiscalMonth`
- `Ledger.DateKey`
- `Ledger.AccountKey`
- `Ledger.SignedAmount`
- `Ledger.IsAdjustment`

These decisions confirm deterministic field mappings. They do not waive semantic or data-quality acceptance testing.

## Gap and scope decisions

The following targets are confirmed gaps with required action `acquire_or_source` and scope state `accepted_for_scope`:

- `Account.AccountGroup`
- `Ledger.CostCentre`
- `Ledger.CurrencyCode`

The recorded reasons state that no current evidence was available and the gap was accepted for phase-two scope.

## Decision boundary

The decisions do not establish:

- which upstream source will be used;
- transformation, join or slowly changing dimension design;
- implementation completion;
- production acceptance;
- broader target requirements not represented by the field-level workbook.