One-to-One Crosswalk Table¶
Artifact — instantiates Lossless Bijective Mapping Design
A table that pairs each source member with exactly one target member and supports inverse lookup.
A one-to-one crosswalk table is the concrete two-column artifact that is the mapping: each row pairs one source member with exactly one target member, and the table taken as a whole enumerates both sets and states the correspondence between them. Its defining property is that it holds the structure of the bijection in inspectable, regenerable form — you can read every pairing, count both columns, and traverse a row in either direction — but it says nothing about time. It is a snapshot of the rule, not a governed process. The crosswalk is what you hand to someone who asks "what maps to what?": the explicit rule, the domain listed down one side, the codomain listed down the other. Everything about lifecycle — how pairings change, what happens to the ones that break — belongs to other mechanisms; the table's job is to make the correspondence itself legible and exact at rest.
Example¶
A finance team consolidating two subsidiaries onto one general ledger must reconcile two legacy charts of accounts into a single new chart, and regulation requires the mapping be exact and one-to-one: every old account maps to precisely one new account, and every new account traces back to precisely one old one, so restated prior-year figures reconcile to the penny. The team builds a one-to-one crosswalk table. Down the left it enumerates the source set — all 812 legacy account codes. Down the right it enumerates the target set — the 812 new codes. Each row states the pairing and the rationale for it.
Because the artifact lays both sets side by side, its defects are visible on inspection: two legacy accounts that both point at new code 4100 jump out as a violation of the one-to-one requirement, and a new code with no legacy source is a blank left cell. The controller uses the table to see the correspondence, sign off on each pairing, and hand auditors a single sheet that reads in both directions. It deliberately does not track what happens next quarter when an account is retired — that is somebody else's mechanism. The crosswalk is the exact rule, frozen and readable.
How it works¶
- Enumerate both sides explicitly. The table lists the full source set and the full target set, so cardinality and coverage are checkable by eye, not inferred.
- One row, one pairing. Each row binds exactly one source to exactly one target; the rule is the table, not a hidden heuristic, so every pairing can be inspected and regenerated.
- Readable in both directions. Sorted or indexed either way, a row answers "what does this source map to?" and "what maps to this target?" symmetrically.
- Snapshot, not process. It captures the correspondence at a point in time; change management lives elsewhere.
Tuning parameters¶
- Grain of the members — whether rows pair individual identifiers or coarser buckets. Finer grain preserves more distinctions but enlarges the table and its maintenance.
- Rationale capture — how much per-row justification is recorded alongside the pairing. Rich rationale makes the table auditable; bare pairs are lighter but opaque.
- Materialization — a hand-curated sheet versus a generated table from a transformation rule. Generation scales and stays consistent; hand curation handles idiosyncratic pairings a rule can't express.
- Sort/index orientation — which side is primary for lookup. Optimizing one direction can make the reverse direction a full scan unless a second index is kept.
When it helps, and when it misleads¶
Its strength is legibility: the entire correspondence sits on one surface where a human or a checker can see every pairing, count both columns, and confirm the rule is exactly one-to-one before anything downstream depends on it. For a bounded, relatively stable mapping it is the simplest artifact that makes bijection inspectable.
Its honest failure mode is that a table looks authoritative even when the underlying relationship was never bijective — the medical-coding world's hard lesson, where "crosswalks" between code systems are routinely many-to-one or one-to-many and a one-to-one table forced over them silently loses or fabricates distinctions.[n1] The classic misuse is treating the crosswalk as live: because it carries no change machinery, a table trusted after the source or target set has shifted is quietly stale, mapping to members that no longer exist. The guarding discipline is to confirm the relationship really is one-to-one before building the table (relabel it if not), and to pair it with a governance mechanism the moment either set starts to change rather than editing the snapshot in place.
How it implements the components¶
mapping_rule— the table is the rule: an explicit, inspectable, regenerable statement of which source pairs with which target.domain_set_specification— one column enumerates the full source set, bounding what must be mapped from.codomain_set_specification— the other column enumerates the full target set, bounding what must be covered.
It does not implement change_synchronization_rule, exception_register, or proof_or_audit_record — pairing lifecycle, quarantine, and audit history are owned by its artifact-cluster twin ID Mapping Register; the crosswalk is the static structure, the register governs its change over time.
Related¶
- Instantiates: Lossless Bijective Mapping Design — it is the archetype's core structural artifact, the mapping made legible.
- Sibling mechanisms: ID Mapping Register · Bijection Test Suite · Inverse Index · Orphan Target Scan · Round-Trip Migration Test · Reversible Encoder–Decoder Pair · Unique-Constraint Pair · Mapping Exception Queue
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: One-to-One Crosswalk Table operates as a static representation, map, specification, schema, or prospective plan that externalizes information because it a table that pairs each source member with exactly one target member and supports inverse lookup.
Independent corroboration: The frozen evidence defines One-to-One Crosswalk Table as 'A table that pairs each source member with exactly one target member and supports inverse lookup', 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: Knowledge-organization and records practice developed crosswalks between classification schemes, including explicit equivalence and reversibility constraints.
Related originating lineages:
- Computer Science & Software Engineering — Data integration operationalized one-to-one mappings, keys, inverse lookup, and validation against accidental many-valued relationships.
- Mathematics — Bijections supply the exact one-to-one and inverse-lookup structure.
Review resolution: Both independent reviews agree on primary origin library_information_science; reconciliation resolves alternate_origin_disagreement, origin_mode_disagreement, encyclopedia_synthesis_disagreement. Formative alternate lineages retained: computer_science, mathematics. The broader reach of later applications is kept separate as domain_reach=multi_domain; origin_mode=cross_disciplinary_synthesis describes the historical relationship among lineages. Confidence is conservatively reconciled to high, and encyclopedia_synthesis=true preserves the reviewers' boundary judgment.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] In data integration a crosswalk maps members of one scheme to another; the well-known General Equivalence Mappings between the ICD-9 and ICD-10 code systems are famously not one-to-one, containing many-to-one and one-to-many links. Forcing a one-to-one table over a relationship that is genuinely many-valued is the archetype's "forced bijection" failure in miniature. ↩