Epic 8 — Auto schema mapping to a canonical layout (the differentiator)

[xt0n1-t3ch]

Research finding: every sender uses different column names/codes, and rivals admit the mapping step usually stays manual. Automating it well is where we out-class the field.

Scope

• Canonical reinsurance schema (premium + claims bordereau fields) as the target layout.
• Auto-map a documents detected headers to canonical fields ("GWP"/"Gross Written Premium"/"Premium_Gross" -> Premium) with a confidence per mapping.\n- [ ] One-click correction of a mapping that is remembered per sender (learned templates).\n- [ ] Normalize values: dates, currencies (ISO 4217), status codes.\n- [ ] Show the mapping visibly in Review so the user trusts it.\n\nGrounds: docs/research/reinsurance-landscape.md (sections 3-5,7).

[xt0n1-t3ch]

Starting #34 implementation.

Plan:

• Hybrid EF mapper: static canonical aliases plus learned sender/domain overrides.
• Persist mapping evidence per document and learned overrides keyed by sender/domain + normalized source header.
• Surface mappings in Review with confidence and correction path.
• Validate with build, format, solution tests, E2E, and browser proof before PR/close.

Baseline: main at a80aaec-compatible clean state; dotnet build Reva.slnx -warnaserror passed with 0 warnings.

[xt0n1-t3ch]

#34 progress update

Implemented and locally validated the hybrid schema-mapping slice:

• Contracts expose schemaMappings on document details plus mapping corrections in review decisions.
• Infrastructure now maps source headers with learned sender/domain overrides first, then static aliases, then bounded fuzzy matching, with unmapped low-confidence rows preserved for review.
• EF persistence added for per-document mapping evidence and learned sender mappings.
• Review UI shows a Schema mapping panel with source header -> canonical field, confidence/source, normalized value, sender key, and correction staging.
• Mapping correction path persists learned rules and applies the corrected value to the canonical field.

Proof run:

• dotnet build Reva.slnx -warnaserror -> passed, 0 warnings.
• dotnet format Reva.slnx --verify-no-changes -> passed.
• dotnet test Reva.slnx -> passed, 28 unit + 14 integration.
• dotnet build tests/Reva.E2E/Reva.E2E.csproj -> passed, 0 warnings.
• dotnet test tests/Reva.E2E/Reva.E2E.csproj --no-build -> passed, 3 e2e.
• Browser proof at http://localhost:5187: uploaded a sender-specific .eml, verified Schema mapping panel, staged GWP -> Claims correction, saved it, saw Corrected 99% and Claims marked Reviewed; console errors []. Screenshots saved locally under artifacts/schema-mapping-*-proof.png.

[xt0n1-t3ch]

#34 close proof

Merged via PR #40 into main at a7924ce.

Acceptance mapping:

• Canonical reinsurance schema mapping target added to document details as schemaMappings.
• Header auto-mapping implemented for variants such as GWP, Gross Written Premium, Premium_Gross, Cedant Co, and CCY with confidence and source (alias, fuzzy, learned, unmapped).
• Learned sender/domain overrides persist in EF and take precedence for subsequent documents from the same sender.
• Review UI shows the Schema mapping panel and lets analysts correct mappings; corrected mappings mark the canonical field reviewed and save the learned rule.
• Values normalize for money, percent, currency, dates, and simple status codes.

Proof:

• Local dotnet build Reva.slnx -warnaserror passed with 0 warnings.
• Local dotnet format Reva.slnx --verify-no-changes passed.
• Local dotnet test Reva.slnx passed: 28 unit + 14 integration.
• Local dotnet build tests/Reva.E2E/Reva.E2E.csproj passed with 0 warnings.
• Local pwsh tests/Reva.E2E/bin/Debug/net10.0/playwright.ps1 install chromium passed.
• Local dotnet test tests/Reva.E2E/Reva.E2E.csproj --no-build passed: 3 e2e.
• Browser proof: uploaded sender .eml, verified Schema mapping panel, corrected GWP -> Claims, saved, observed Corrected 99% and Claims marked Reviewed; console errors [].
• CI on PR feat(schema): learn sender-specific mappings #40 passed: dotnet and e2e.