Scenario 6 of 12

Semarchy disagrees with an approved correction

Florence's surname correction was approved in Profile. Semarchy has since sent a different surname.

Shows: The approved Profile value stays on the face while the disagreement is resolved. Arrival order is not a survivorship rule, so the newer external value does not win by being newer.

Source: Edge-case example 8 — Semarchy disagrees with an approved Profile correction in docs/mdm/mdm-profile-logical-mapping.md

Personal details

Two ways this could be shown

Some details Camden holds are being checked and are not on this page. Whether the Citizen is told that is an open question — deferral 9 in the logical mapping defers it explicitly, and withholding is silent in the current model. Neither version below is decided.

Silent

The value is simply absent. Truthful to the model as written, and impossible for the Citizen to distinguish from never having been held.

Preferred name: Flo
You added this; Change preferred name
Name: Florence N Okonkwo
From Camden records; Request a correction name
Date of birth: 3 March 1988
From Camden records; Request a correction date of birth
Email address: florence.adeyemi@example.com
You added this
Used for 3 communications.; Change email address
Phone number: 07700 900 118
You added this
Used for 2 communications.; Change phone number
Address: Flat 4, 12 Prowse Place, London NW1 9PH
You added this
Used for 1 communication.; Change address

Disclosed

A short explanation and a case reference. Invented copy — no agreed wording exists.

Preferred name: Flo
You added this; Change preferred name
Name: Florence N Okonkwo
From Camden records Being checked
Your name is correct here. We are updating our other records to match, which can take a few days. Reference scc-0009; Request a correction name
Date of birth: 3 March 1988
From Camden records; Request a correction date of birth
Email address: florence.adeyemi@example.com
You added this
Used for 3 communications.; Change email address
Phone number: 07700 900 118
You added this
Used for 2 communications.; Change phone number
Address: Flat 4, 12 Prowse Place, London NW1 9PH
You added this
Used for 1 communication.; Change address

Sign-in details

Your login email, passkeys and two-factor settings are held by the sign-in service, not in your Profile. Changing your email address here does not change the address you sign in with.

Manage how you sign in

Behind the scenes

Not part of the Citizen view. Ticket 01 keeps source-system detail off the wire entirely — this pane exists so the sync behaviour is legible to us, not to Florence.

citizenId: ctz-7k3m9p2x4v8r6t1q5w0n
identity_confidence: verified

Fields

preferredName

Composed envelope

value: Flo
provenance: citizen-provided
action: edit
updatedAt: 2026-07-02T09:12:00Z

Stored values (1)

value: Flo
provenance: citizen-provided
state: current
updatedAt: 2026-07-02T09:12:00Z
origin.system: Profile

name

Composed envelope

value: Florence N Okonkwo
provenance: camden-held
action: request-correction
updatedAt: 2026-08-02T10:15:00Z
suppressed: withheld

Stored values (2)

value: Florence N Okonkwo
provenance: camden-held
state: current
updatedAt: 2026-08-02T10:15:00Z
origin.system: Profile
origin.recordId: approved correction cr-0087

value: [disputed value not shown]
provenance: camden-held
state: withheld
updatedAt: 2026-08-06T02:14:00Z
origin.system: Semarchy
origin.recordId: PersonID 88431
origin.sourceVersion: 15
linkId: lnk-ctax
caseId: scc-0009

Disagrees with an approved correction. Held pending the Synchronization Conflict Case.

dateOfBirth

Composed envelope

value: 3 March 1988
provenance: camden-held
action: request-correction
updatedAt: 2026-07-11T02:14:00Z

Stored values (1)

value: 3 March 1988
provenance: camden-held
state: current
updatedAt: 2026-07-11T02:14:00Z
origin.system: Semarchy
origin.recordId: PersonID 88431
origin.sourceVersion: 12
origin.receivedAt: 2026-07-11T02:14:00Z
linkId: lnk-ctax

contactEmail

Composed envelope

value: florence.adeyemi@example.com
provenance: citizen-provided
action: edit
updatedAt: 2026-06-14T11:41:00Z
confirmation: confirmed

Stored values (1)

value: florence.adeyemi@example.com
provenance: citizen-provided
state: current
updatedAt: 2026-06-14T11:41:00Z
confirmation: confirmed
origin.system: Profile

phone

Composed envelope

value: 07700 900 118
provenance: citizen-provided
action: choose-or-add
updatedAt: 2026-06-14T11:41:00Z
selectedBy: citizen
confirmation: confirmed
candidates: 1

Stored values (1)

value: 07700 900 118
provenance: citizen-provided
state: current
updatedAt: 2026-06-14T11:41:00Z
label: Mobile
confirmation: confirmed
origin.system: Profile

Primary Selection points at ph-1, chosen by citizen. It is a pointer — it overwrites nothing.

address

Composed envelope

value: Flat 4, 12 Prowse Place, London NW1 9PH
provenance: citizen-provided
action: choose-or-add
updatedAt: 2026-06-20T15:05:00Z
selectedBy: citizen
candidates: 1

Stored values (1)

value: Flat 4, 12 Prowse Place, London NW1 9PH
provenance: citizen-provided
state: current
updatedAt: 2026-06-20T15:05:00Z
label: Home address
origin.system: Profile

Primary Selection points at ad-1, chosen by citizen. It is a pointer — it overwrites nothing.

Integration Links

lnk-ctax active
system
Semarchy
identifier
Council Tax account CT-4471902
policy
Council Tax Reference Link Policy v2
linkedAt
2026-06-28T10:02:00Z
externalVersion
12
caseId
scc-0009
lnk-crm active
system
CRM
identifier
CRM Person 4821
policy
CRM Reference Link Policy v1
linkedAt
2026-06-28T10:02:00Z
externalVersion
17

Cases

scc-0009 — synchronization-conflict
Semarchy sent a surname that disagrees with an approved Profile correction. Neither side is overwritten.
openedAt
2026-08-06T02:14:30Z
affectedFields
name

Sync trace

Source Update Command · Semarchy → Profile
2026-08-06T02:14:00Z
Conflicting surname received while a correction is authoritative
sourceVersion
15
outcome
queued as a Synchronization Conflict Case
note
Cross-system arrival time is not a survivorship rule.

Event names are illustrative. The domain event catalogue and integration notifications are tickets 09 and 10, both open and blocked — only profile.personal-details.changed has been written down, and published events are pointer-only by design.