AI-authoreddecisioncurrent

Recorded mapping and scope decisions

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.

fde-finance.recorded-decisions · wiki_7c268dbf7f8b78844080cae53f6f0a0e

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 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 gaps were accepted for phase-two scope.

## No recorded decision

There is no mapping or scope decision for:

- `Ledger.JournalSource`
- `Ledger.ApprovalStatus`

Their upstream availability comes from consultant evidence, not from the mapping decision set.

## Decision boundary

The recorded decisions do not establish:

- upstream source design;
- transformation, join or effective-dating logic;
- implementation completion;
- production acceptance;
- broader target requirements outside the workbook's field list.