OverviewMS360 SchemaTest MS360 InstanceEntitiesStandardization RulesConflict RulesAssociation RulesResolved InstancesWrite-back Audit
00 · Overview

Normalization, association & standardization

Raw records from 3 source files in the uploaded MS360 test instance are mapped onto canonical entities, standardized, deduplicated and reconciled. Original extracted values are never overwritten.

Raw records (test instance)
11
Resolved instances
16
Flagged for review
3
Auto-resolved
1
Write-back blocks
0

Pipeline

  1. 01
    Map
    MS360 paths → canonical fields
  2. 02
    Standardize
    Geocode, casing, code lookup
  3. 03
    Expand scope
    Discover states, then expand ALL
  4. 04
    Match & reconcile
    Dedup key, survivorship, conflicts
  5. 05
    Write back
    Additive _Resolved_<Entity> block
Last run: never

Entities

  • Location
    ResolvedPer Account
    2 instances
  • WC_Exposure
    ResolvedPer Account
    9 instances
    2 flagged
  • Class_Code
    ReferenceGlobal
    5 instances
    1 flagged

Open questions carried from the spec

OPEN Q 9.1Instance IDs use a placeholder FNV-1a hash of the normalized match key.
OPEN Q 9.2Unconfigured fields default to Flag for Review — not yet confirmed.
OPEN Q 9.3Global dedup scope is selectable but visibly flagged.
OPEN Q 9.4Exposure with no physical location shows Location_Ref = null plus a No_Fixed_Location flag.
OPEN Q 9.5Same-payroll / different-class-code detection is not attempted in v0.