Gold wiki and phase-two scope

# Perform Phase Two — Draft Scope / Statement of Work

## Status and boundary

This document is generated decision support for the second part of the Perform engagement. It defines proposed implementation work; it does not assert that the target architecture has been built or deployed.

## Evidence baseline

- Current observed snapshot: `snapshot_current_e5ecaac9135e1535c70cfe5eb371f6f4` (as at 2026-07-29T14:11:57.332617+00:00)
- Declared target snapshot: `snapshot_target_d6a0a4cec803326d047cca0e7df7333c` (as at 2026-07-29T16:30:24.714Z)
- Confirmed scoped gaps: 3
- Generated scope ID: `scope_b3be9430886a16afe804f214b35374b7`

## Proposed outcomes

Establish the target semantic fields and supporting data identified below, validate their business definitions and grain, implement approved transformations, and provide evidence that each accepted target requirement is satisfied.

## Work packages

### WP-01: Account

Work package ID: `wp_7cedac80751acb6a`

Target requirements:

- `Account.AccountGroup` (String) — Management reporting group above account type. [case `map_585c99c93e6a75765671704027b2d671`, decision `decision_bf078ea6d947223739007e14368dead5`]

Proposed activities:

- Confirm authoritative source, ownership, grain, and refresh expectations.
- Design and implement the required ingestion, transformation, and semantic-model changes.
- Add deterministic reconciliation tests and target-field acceptance evidence.
- Update lineage, documentation, and operational support materials.

Acceptance criteria:

- Each scoped target field is present at the agreed grain and data type.
- Business definitions and calculation rules are approved.
- Refresh and lineage are demonstrated with inspectable receipts.
- Deterministic fixture and reconciliation tests pass.

### WP-02: Ledger

Work package ID: `wp_545dd4daf4e601eb`

Target requirements:

- `Ledger.CostCentre` (String) — Management cost-centre code. [case `map_2e388d52d81ff95f3bbb90fa6772a300`, decision `decision_cbbc1ca63164300470752b1d108c35c0`]
- `Ledger.CurrencyCode` (String) — ISO reporting currency code. [case `map_bea3e0f3dc83febe286bb6ba67319555`, decision `decision_d87d082ec2bd2db6064500968ce65580`]

Proposed activities:

- Confirm authoritative source, ownership, grain, and refresh expectations.
- Design and implement the required ingestion, transformation, and semantic-model changes.
- Add deterministic reconciliation tests and target-field acceptance evidence.
- Update lineage, documentation, and operational support materials.

Acceptance criteria:

- Each scoped target field is present at the agreed grain and data type.
- Business definitions and calculation rules are approved.
- Refresh and lineage are demonstrated with inspectable receipts.
- Deterministic fixture and reconciliation tests pass.

## Assumptions

- Client source-system access and subject-matter experts are available during phase two.
- Confirmed absence in this synthetic run is a test disposition, not a claim about a real client estate.
- Existing mapped fields remain usable unless later evidence triggers revalidation.

## Dependencies and client responsibilities

- Provide authoritative definitions, source access, owners, and security classifications.
- Resolve any client-question cases before their dependent work package is committed.
- Approve semantic definitions and production acceptance criteria.

## Exclusions

- Production implementation is not performed by the current discovery web-app project.
- Items not accepted into `scope_state=accepted_for_scope` are excluded unless added through a later receipt.
- Production support, adoption, and outcome claims require a separate phase-two agreement.

## Traceability

Every target requirement above resolves through its mapping case and decision receipt to the original workbook range and current audit snapshot.

# Perform Phase Two — Draft Scope / Statement of Work

## Status and boundary

This document is generated decision support for the second part of the Perform engagement. It defines proposed implementation work; it does not assert that the target architecture has been built or deployed.

## Evidence baseline

- Current observed snapshot: `snapshot_current_e5ecaac9135e1535c70cfe5eb371f6f4` (as at 2026-07-29T14:11:57.332617+00:00)
- Declared target snapshot: `snapshot_target_f5c276c362cbb7ae57ffe70de95fc2da` (as at 2026-07-29T16:30:23.991Z)
- Confirmed scoped gaps: 0
- Generated scope ID: `scope_e566596db326387fe2d1e27a21c0e2f9`

## Proposed outcomes

Establish the target semantic fields and supporting data identified below, validate their business definitions and grain, implement approved transformations, and provide evidence that each accepted target requirement is satisfied.

## Work packages

No confirmed gaps have been accepted into scope.

## Assumptions

- Client source-system access and subject-matter experts are available during phase two.
- Confirmed absence in this synthetic run is a test disposition, not a claim about a real client estate.
- Existing mapped fields remain usable unless later evidence triggers revalidation.

## Dependencies and client responsibilities

- Provide authoritative definitions, source access, owners, and security classifications.
- Resolve any client-question cases before their dependent work package is committed.
- Approve semantic definitions and production acceptance criteria.

## Exclusions

- Production implementation is not performed by the current discovery web-app project.
- Items not accepted into `scope_state=accepted_for_scope` are excluded unless added through a later receipt.
- Production support, adoption, and outcome claims require a separate phase-two agreement.

## Traceability

Every target requirement above resolves through its mapping case and decision receipt to the original workbook range and current audit snapshot.

# Perform Phase Two — Draft Scope / Statement of Work

## Status and boundary

This document is generated decision support for the second part of the Perform engagement. It defines proposed implementation work; it does not assert that the target architecture has been built or deployed.

## Evidence baseline

- Current observed snapshot: `snapshot_current_e5ecaac9135e1535c70cfe5eb371f6f4` (as at 2026-07-29T14:11:57.332617+00:00)
- Declared target snapshot: `snapshot_target_a90893d3e51b15aa481838814d77953a` (as at 2026-07-29T16:30:23.211Z)
- Confirmed scoped gaps: 8
- Generated scope ID: `scope_df32bfd8cdb4010d3d6c234ab64fbcc2`

## Proposed outcomes

Establish the target semantic fields and supporting data identified below, validate their business definitions and grain, implement approved transformations, and provide evidence that each accepted target requirement is satisfied.

## Work packages

### WP-01: Customer

Work package ID: `wp_6019e8d5b5606546`

Target requirements:

- `Customer.CustomerIdentifier` (String) — Enterprise customer identity. [case `map_22789fbadee3ca89d4b9c14c8ca91f2d`, decision `decision_b384541acf40de0d21bffe114544a6e5`]
- `Customer.CustomerSegment` (String) — Commercial segment. [case `map_22d85e8373e66341bcf9fd9e64763a54`, decision `decision_7d5ca440c666f85f71f416548e00eca3`]
- `Customer.RelationshipOwner` (String) — Accountable relationship owner. [case `map_1a6c8531950e464ee04b9fa6b6a60b52`, decision `decision_22792f376b3d733a1481f0b503928d27`]

Proposed activities:

- Confirm authoritative source, ownership, grain, and refresh expectations.
- Design and implement the required ingestion, transformation, and semantic-model changes.
- Add deterministic reconciliation tests and target-field acceptance evidence.
- Update lineage, documentation, and operational support materials.

Acceptance criteria:

- Each scoped target field is present at the agreed grain and data type.
- Business definitions and calculation rules are approved.
- Refresh and lineage are demonstrated with inspectable receipts.
- Deterministic fixture and reconciliation tests pass.

### WP-02: SalesMetrics

Work package ID: `wp_af77eeaa1e07c58f`

Target requirements:

- `SalesMetrics.Customer Lifetime Value` (Decimal) — Expected customer lifetime value. [case `map_e49b822ab2b1f4fadd00e288b33202ff`, decision `decision_f0fca392afb61f817a0b8f4caf2f9575`]
- `SalesMetrics.Gross Order Intake` (Decimal) — Gross booked order value. [case `map_34a7ebe3f533d0e33c0b7d52e8a8f714`, decision `decision_b7474f5c2156a8656d05e9eb3bfdc05d`]

Proposed activities:

- Confirm authoritative source, ownership, grain, and refresh expectations.
- Design and implement the required ingestion, transformation, and semantic-model changes.
- Add deterministic reconciliation tests and target-field acceptance evidence.
- Update lineage, documentation, and operational support materials.

Acceptance criteria:

- Each scoped target field is present at the agreed grain and data type.
- Business definitions and calculation rules are approved.
- Refresh and lineage are demonstrated with inspectable receipts.
- Deterministic fixture and reconciliation tests pass.

### WP-03: SalesOrder

Work package ID: `wp_6d66779865cd69c9`

Target requirements:

- `SalesOrder.OrderGrossValue` (Decimal) — Gross order value before discounts. [case `map_39e9a9df534e90740e177deb744c1474`, decision `decision_ea6f478e34e633be0685ff23137cb557`]
- `SalesOrder.OrderIdentifier` (String) — Customer order identity. [case `map_61ee8482ac8f962828fc43454bea214c`, decision `decision_7e5cb4ea8d661ec015069f8f3688b11e`]
- `SalesOrder.SalesChannel` (String) — Order acquisition channel. [case `map_43ba9ced173b1cc86eef95b8f35cc9da`, decision `decision_612ae4fa139ef126a73b1455004e5fd6`]

Proposed activities:

- Confirm authoritative source, ownership, grain, and refresh expectations.
- Design and implement the required ingestion, transformation, and semantic-model changes.
- Add deterministic reconciliation tests and target-field acceptance evidence.
- Update lineage, documentation, and operational support materials.

Acceptance criteria:

- Each scoped target field is present at the agreed grain and data type.
- Business definitions and calculation rules are approved.
- Refresh and lineage are demonstrated with inspectable receipts.
- Deterministic fixture and reconciliation tests pass.

## Assumptions

- Client source-system access and subject-matter experts are available during phase two.
- Confirmed absence in this synthetic run is a test disposition, not a claim about a real client estate.
- Existing mapped fields remain usable unless later evidence triggers revalidation.

## Dependencies and client responsibilities

- Provide authoritative definitions, source access, owners, and security classifications.
- Resolve any client-question cases before their dependent work package is committed.
- Approve semantic definitions and production acceptance criteria.

## Exclusions

- Production implementation is not performed by the current discovery web-app project.
- Items not accepted into `scope_state=accepted_for_scope` are excluded unless added through a later receipt.
- Production support, adoption, and outcome claims require a separate phase-two agreement.

## Traceability

Every target requirement above resolves through its mapping case and decision receipt to the original workbook range and current audit snapshot.