Mapping Conflict Matrix¶
Artifact — instantiates Mapping Reconciliation
A table that lists each contested source element, competing target mappings, conflict type, selected rule, decision, confidence, and exception status.
Mapping Conflict Matrix is the artifact at the center of a reconciliation — the persistent, structured table that holds one row per contested element and, across its columns, the whole shape of the disagreement and its resolution: the competing target mappings, the conflict type, the reconciliation rule that was applied, the decision that resulted, a confidence rating, and the exception status. Its defining feature is that it is a durable object, not an activity: where a workshop is the meeting and a review is the procedure, the matrix is the thing they write into and that outlives them. Its value is that it forces every contested correspondence into the same disciplined schema, so that "what did we decide about this row, on what rule, and how sure are we" is answerable at a glance long after the deciders have moved on. It is a container for decisions, not a decider.
Example¶
Two retailers merge their e-commerce catalogs, and their product-category trees collide: A files a cast-iron skillet under Kitchen > Cookware, B under Home > Cooking > Pans. A Mapping Conflict Matrix is stood up with a row per contested category. For the skillet's category, the columns read: source = A: Kitchen>Cookware; competing targets = B: Home>Cooking>Pans, B: Home>Cooking>Bakeware; conflict type = granularity split (A's one node maps to two of B's); rule applied = "prefer the more specific target when unambiguous"; decision = Home>Cooking>Pans; confidence = high; exception = none. Three rows down, a category A: Seasonal has no stable target at all — the matrix records conflict type = no valid target, decision = defer, confidence = low, exception = flagged: route to manual triage. The finished matrix is not a discussion and not a test; it is the auditable ledger that says, for every contested element, exactly what was chosen and why — the reconciled catalog map made inspectable.
How it works¶
- One row per contested element. The unit of the artifact is the disputed source item; uncontested mappings stay out, keeping the matrix focused on where reconciliation actually happened.
- Fixed columns enforce completeness. Competing targets, conflict type, rule, decision, confidence, and exception status are mandatory fields, so no row can record a decision without also recording its basis and its uncertainty.
- The decision column is the canonical pick. For each row, exactly one target is marked as the reconciled choice for the defined purpose; the losing candidates remain visible beside it rather than being erased.
- Confidence and exception travel with the decision. Every chosen correspondence carries how sure the deciders were and whether it is a clean rule or a flagged special case.
Tuning parameters¶
- Column set — the minimum {source, target, decision} versus a full {conflict type, rule, confidence, exception, provenance}. Richer columns make the artifact more auditable but heavier to fill and maintain.
- Row scope — contested elements only, or every element for completeness. Contested-only keeps the matrix sharp; full coverage doubles as documentation but buries the conflicts.
- Confidence scale — binary (sure / unsure) versus graded. Graded confidence supports downstream triage but invites false precision in the rating itself.
- Structure — flat table versus linked/relational (rows referencing rule definitions and provenance records). Linked structure scales and stays consistent; a flat sheet is quicker to start and quicker to rot.
When it helps, and when it misleads¶
Its strength is inspectability: a single well-formed matrix answers "what did we decide, on what rule, how confident, and what's the exception" for hundreds of correspondences without reconvening anyone. It is the artifact that makes a reconciliation auditable and hand-offable, and its fixed columns quietly prevent the most common gap — a decision recorded with no rule or no confidence attached.
Its failure mode is reification[n1]: mistaking the tidy table for the reconciliation itself. A filled matrix looks authoritative, which tempts teams to treat a confidently-worded row as a validated one — but the artifact only records what was decided, not whether the decision works on real data. A classic misuse is freezing the matrix and letting it drift as source categories change, so the ledger silently describes a mapping that no longer exists. The guarding discipline is to treat the matrix as a record awaiting validation, keep its confidence column honest, and pair it with an external check rather than letting the table's neatness stand in for correctness.
How it implements the components¶
Mapping Conflict Matrix realizes the durable record face of the archetype — the columns of a decision table:
mapping_conflict_inventory— the matrix is the inventory in tabular form: one row per contested element, tagged with its conflict type.reconciliation_rule— the "rule applied" column captures which resolution rule governed each row, keeping the logic inspectable and repeatable.canonical_mapping— the "decision" column records the single chosen correspondence per row that downstream use should adopt for the defined purpose.
It does NOT implement stakeholder_review_panel — convening the accountable humans who fill it is Crosswalk Reconciliation Workshop — nor validation_test, proving the decisions hold on real cases, which is Code Crosswalk Validation. The matrix stores decisions; it neither convenes nor tests them.
Related¶
- Instantiates: Mapping Reconciliation — the persistent artifact that holds a reconciliation's decisions.
- Consumes: Crosswalk Reconciliation Workshop — the matrix is the ledger a workshop (or review) writes its decisions into.
- Sibling mechanisms: Schema Mapping Review · Ontology Alignment Session · Translation Memory Review · Code Crosswalk Validation · Standard-Setting Process · Reconciliation Report
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Mapping Conflict Matrix operates as a non-executable information artifact that externalizes static or prospective structure because it a table that lists each contested source element, competing target mappings, conflict type, selected rule, decision, confidence, and exception status.
Independent corroboration: The frozen evidence defines Mapping Conflict Matrix as 'A table that lists each contested source element, competing target mappings, conflict type, selected rule, decision, confidence, and exception status', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Crosswalks, authority control, and explicit reconciliation of competing classifications have a strong library and information science lineage.
Related originating lineages:
- Data Science & Analytics — Schema matching and data integration contribute automated candidates, confidence, and exception status.
- Organizational & Management Science — Decision ownership, conflict type, and chosen-rule records materially shape the governance matrix.
Review resolution: Both independent reviews assign primary provenance to library_information_science. The queued secondary differences (reported_ambiguity, alternate_origin_disagreement) are reconciled by retaining data_science, organizational_management only as formative or independently established lineage(s), not merely as application domains. origin_mode=cross_disciplinary_synthesis records the provenance relationship, while domain_reach=multi_domain separately records applicability breadth. confidence=medium preserves the more cautious assessment, and encyclopedia_synthesis=true records whether either reviewer identified a corpus-specific synthesis.
Attribution caveat: The exact matrix is a synthesized artifact rather than a canonical named standard.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] Treating an abstraction or representation as if it were the concrete reality it stands for. A conflict matrix is especially prone to it: the table's neat, confident rows invite the reader to trust the record of a decision as though it were the verification of one. ↩