Two systems and one member each one rules its own fields

Goal Show each field of a member from the system that rules it, without hiding a disagreement.

A health insurer keeps its members in its contract system and in its portal. With one source order, one of them is always wrong.

the address comes from the portal, the plan from the contract system;
every disagreement stays listed;
it leaves the list when the source settles it.

lumnik Open
Insurance
Integration
Connector
Entity

gestion-night1.csv

member_no,full_name,plan,effective_date,street,city
M-1001,DUPONT Claire,ESSENTIEL,2024-01-01,4 rue des Lilas,Lyon
M-1002,MARTIN Paul,CONFORT,2023-06-01,12 avenue Foch,Villeurbanne
M-1003,BERNARD Lucie,CONFORT,2025-03-01,7 place Bellecour,Lyon
M-1004,PETIT Hugo,ESSENTIEL,2022-09-01,3 chemin du Moulin,Vienne
M-1005,ROUX Anna,INTEGRAL,2024-11-01,18 quai Saint-Antoine,Lyon
M-1006,FAURE Léo,CONFORT,2021-02-01,9 rue Garibaldi,Lyon

portail-night1.csv

member_no,full_name,plan,street,city,email
M-1001,Dupont Claire,ESSENTIEL,4 rue des Lilas,Lyon,claire.dupont@example.org
M-1002,MARTIN Paul,CONFORT,25 rue Paul Bert,Lyon,paul.martin@example.org
M-1003,BERNARD Lucie,ESSENTIEL,7 place Bellecour,Lyon,lucie.bernard@example.org
M-1004,PETIT Hugo,ESSENTIEL,3 chemin du Moulin,Vienne,
M-1005,ROUX Anna,INTEGRAL,41 cours Gambetta,Lyon,anna.roux@example.org
M-1006,FAURE Léo,CONFORT,9 rue Garibaldi,Lyon,leo.faure@example.org

manifests/10-gestion.yaml

apiVersion: connectors.lumnik.io/v1kind: Connectormetadata:  name: scenario-member-gestion-a  connector_type: csv-file  scopes: [adhesion]spec:  transport:    kind: local    path: /tmp/lumnik-scenario/two-systems-one-member/a/gestion.csv  parser:    has_header: true  after_process: none

manifests/11-portail.yaml

apiVersion: connectors.lumnik.io/v1kind: Connectormetadata:  name: scenario-member-portail-a  connector_type: csv-file  scopes: [adhesion]spec:  transport:    kind: local    path: /tmp/lumnik-scenario/two-systems-one-member/a/portail.csv  parser:    has_header: true  after_process: none

$ lm apply -f /Users/macspok/eclipse-workspace/lumnik-scenario/scenarios/two-systems-one-member/manifests/10-gestion.yaml
Applied connector "scenario-member-gestion-a" — 1 endpoint

$ lm apply -f /Users/macspok/eclipse-workspace/lumnik-scenario/scenarios/two-systems-one-member/manifests/11-portail.yaml
Applied connector "scenario-member-portail-a" — 1 endpoint

$ lm connector run scenario-member-gestion-a
run scheduled: 9d4c5bb4-da4b-45cc-848b-436d0a114551

$ lm run get 9d4c5bb4-da4b-45cc-848b-436d0a114551
ID        CONNECTOR                  ENDPOINT  STATUS     IN  OUT  SKIPPED  DEAD-LETTERS  STARTED           ENDED
9d4c5bb4  scenario-member-gestion-a  default   Completed  6   6    0        0             2026-11-03 16:59  2026-11-03 16:59

$ lm connector run scenario-member-portail-a
run scheduled: 51c141e6-e94f-42c5-912e-58cad7d08873

$ lm run get 51c141e6-e94f-42c5-912e-58cad7d08873
ID        CONNECTOR                  ENDPOINT  STATUS     IN  OUT  SKIPPED  DEAD-LETTERS  STARTED           ENDED
51c141e6  scenario-member-portail-a  default   Completed  6   6    0        0             2026-11-03 16:59  2026-11-03 16:59

manifests/20-member.yaml

kind: Entityname: member_alabel: Adhérentdescription: "One member across the contract system and the member portal."scopes: [adhesion]match: [member_no]sources:  - table: t_scenario_member_gestion_a    map:      member_no: member_no      full_name: full_name      plan: plan      effective_date: effective_date      street: street      city: city  - table: t_scenario_member_portail_a    map:      member_no: member_no      full_name: full_name      plan: plan      street: street      city: city      email: email

$ lm entity apply -f /Users/macspok/eclipse-workspace/lumnik-scenario/scenarios/two-systems-one-member/manifests/20-member.yaml
Applied entity "member_a" → connector."v_member_a"

$ lm entity get member_a --filter member_no=M-1002
MEMBER_NO  FULL_NAME    PLAN     EFFECTIVE_DATE  STREET          CITY          EMAIL                    _CONFLICTS
M-1002     MARTIN Paul  CONFORT  2023-06-01      12 avenue Foch  Villeurbanne  paul.martin@example.org  {"city": [{"src": "t_scenario_member_gestion_a", "value": "Villeurbanne"}, {"src": "t_scenario_member_portail_a", "value": "Lyon"}], "street": [{"src": "t_scenario_member_gestion_a", "value": "12 avenue Foch"}, {"src": "t_scenario_member_portail_a", "value": "25 rue Paul Bert"}]}

$ lm conflicts list --entity member_a
ENTITY    KEY     COLUMNS      SOURCES
member_a  M-1001  full_name    t_scenario_member_gestion_a,t_scenario_member_portail_a
member_a  M-1002  city,street  t_scenario_member_gestion_a,t_scenario_member_portail_a
member_a  M-1003  plan         t_scenario_member_gestion_a,t_scenario_member_portail_a
member_a  M-1005  street       t_scenario_member_gestion_a,t_scenario_member_portail_a

manifests/30-member-prefer.yaml

kind: Entityname: member_alabel: Adhérentdescription: "One member across the contract system and the member portal."scopes: [adhesion]match: [member_no]sources:  - table: t_scenario_member_gestion_a    map:      member_no: member_no      full_name: full_name      plan: plan      effective_date: effective_date      street: street      city: city  - table: t_scenario_member_portail_a    map:      member_no: member_no      full_name: full_name      plan: plan      street: street      city: city      email: emailcolumns:  street:    prefer: t_scenario_member_portail_a  city:    prefer: t_scenario_member_portail_a

$ lm entity apply -f /Users/macspok/eclipse-workspace/lumnik-scenario/scenarios/two-systems-one-member/manifests/30-member-prefer.yaml
Applied entity "member_a" → connector."v_member_a"

$ lm entity get member_a --filter member_no=M-1002
MEMBER_NO  FULL_NAME    PLAN     EFFECTIVE_DATE  STREET            CITY  EMAIL                    _CONFLICTS
M-1002     MARTIN Paul  CONFORT  2023-06-01      25 rue Paul Bert  Lyon  paul.martin@example.org  {"city": [{"src": "t_scenario_member_portail_a", "value": "Lyon"}, {"src": "t_scenario_member_gestion_a", "value": "Villeurbanne"}], "street": [{"src": "t_scenario_member_portail_a", "value": "25 rue Paul Bert"}, {"src": "t_scenario_member_gestion_a", "value": "12 avenue Foch"}]}

$ lm entity get member_a --filter member_no=M-1003
MEMBER_NO  FULL_NAME      PLAN     EFFECTIVE_DATE  STREET             CITY  EMAIL                      _CONFLICTS
M-1003     BERNARD Lucie  CONFORT  2025-03-01      7 place Bellecour  Lyon  lucie.bernard@example.org  {"plan": [{"src": "t_scenario_member_gestion_a", "value": "CONFORT"}, {"src": "t_scenario_member_portail_a", "value": "ESSENTIEL"}]}

gestion-night2.csv

member_no,full_name,plan,effective_date,street,city
M-1001,DUPONT Claire,ESSENTIEL,2024-01-01,4 rue des Lilas,Lyon
M-1002,MARTIN Paul,CONFORT,2023-06-01,25 rue Paul Bert,Lyon
M-1003,BERNARD Lucie,CONFORT,2025-03-01,7 place Bellecour,Lyon
M-1004,PETIT Hugo,ESSENTIEL,2022-09-01,3 chemin du Moulin,Vienne
M-1005,ROUX Anna,INTEGRAL,2024-11-01,41 cours Gambetta,Lyon
M-1006,FAURE Léo,CONFORT,2021-02-01,9 rue Garibaldi,Lyon

$ lm connector run scenario-member-gestion-a
run scheduled: 348e6025-e88b-4cc2-8386-533395344725

$ lm run get 348e6025-e88b-4cc2-8386-533395344725
ID        CONNECTOR                  ENDPOINT  STATUS     IN  OUT  SKIPPED  DEAD-LETTERS  STARTED           ENDED
348e6025  scenario-member-gestion-a  default   Completed  6   6    0        0             2026-11-03 16:59  2026-11-03 16:59

$ lm conflicts list --entity member_a
ENTITY    KEY     COLUMNS    SOURCES
member_a  M-1001  full_name  t_scenario_member_gestion_a,t_scenario_member_portail_a
member_a  M-1003  plan       t_scenario_member_gestion_a,t_scenario_member_portail_a

Limits

Each column is fused on its own: preferring the portal for street and city does not tie them.
A preference chooses the value shown; it does not settle the dispute at the source.
Synthetic data.

Insurer · members

One member, two systems.

The contract system and the portal.

Six members, two nights

The problem

Who is right?

The contract system for the plan.
The portal for the address.

What is not changed

Both systems stay as they are.

Two exports every night.
No fix in the hub.

The trap

One order for everything.

Contract first keeps the old address.
Portal first loses the right plan.

What had to be written

prefer: t_scenario_member_portail_a

One line.

The source that rules, column by column.
Disagreements stay listed.
A 54-line scenario, three manifests.

The next night

The contract system catches up.

The address disagreements go away.
The rest are for the source to settle.

The limit

Preferring is not settling.

A disagreement is settled at the source.

Try it

The scenario replays locally.

Every step is published with its output.

This scenario runs on lumnik Open, free and open source.

Try lumnik Open →