Not agreed. Screens illustrate proposals in docs/ and .scratch/ , and invent the states those documents leave open.

Back to My Account
Scenario 5 of 12

Two possible existing Profiles

The evidence supplied matches more than one existing Profile. Profile chooses neither.

Shows: Nothing is linked, nothing is consolidated, and no candidate information is revealed — not even that a second candidate resembles the Citizen. The Principal stays on the registration Citizen ID and a Link Review Case decides.

Source: Edge-case example 3 — Two possible existing Profiles in docs/mdm/mdm-profile-logical-mapping.md

Personal details

Preferred name
Not provided
Change preferred name
Name
Florence Adeyemi
You added this
Change name
Date of birth
3 March 1988
You added this
Change 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

You are seeing only the details you have given us yourself. To see and use the details Camden already holds, you need to prove your identity.

Prove your identity

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-2b9v4x7q1n5k8m3p6r0t
identity_confidence
none

Fields

preferredName

Composed envelope

value
null
provenance
null
action
edit

name

Composed envelope

value
Florence Adeyemi
provenance
citizen-provided
action
edit
updatedAt
2026-06-14T11:40:00Z
Stored values (1)
value
Florence Adeyemi
provenance
citizen-provided
state
current
updatedAt
2026-06-14T11:40:00Z
origin.system
Registration

dateOfBirth

Composed envelope

value
3 March 1988
provenance
citizen-provided
action
edit
updatedAt
2026-06-14T11:40:00Z
Stored values (1)
value
3 March 1988
provenance
citizen-provided
state
current
updatedAt
2026-06-14T11:40:00Z
origin.system
Registration

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

None. Nothing camden-held is linked to this Profile.

Cases

  • lrc-0031 — link-review

    Supplied evidence matched more than one existing Profile. Automatic linking is not safe.

    openedAt
    2026-07-15T09:20:00Z
    affectedFields
    none

Sync trace

  • No traffic
    2026-07-15T09:20:00Z

    No link established, so no Source Update Command is accepted

    candidatesConsidered
    2
    revealed
    none
    note
    Candidate count is annotation. It is never shown to the Citizen.

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.