gedcom-fidelity-registry

What problem does it solve?

Prevents silent data loss when evolving the database schema or the GEDCOM import/export code by mechanically requiring that every authored database field either round-trips correctly or is explicitly marked and tested as lossy/excluded.

Core Features & Use Cases

• Round-trip fidelity registry: Declares per (table, column) behavior for GEDCOM 5.5.1 and 7.0, including lossless, lossless-via, lossy, and excluded outcomes.
• CI-enforced coverage: Blocks schema changes that lack registry entries and fails fast when registry entries don’t map to real columns.
• Per-field round-trip tests: Seeds values, exports to GEDCOM, re-imports, and asserts the post-round-trip value matches the registry’s expectation (including conditional expectedAfterRoundTrip logic).
• Clear mechanisms for “lossless-via”: Requires a one-sentence mechanism description so reviewers can verify why identity is preserved.
• Justified exclusions: Supports audit/cache-only exclusions with the expectation they are deliberate and documented.

Quick Start

Use the gedcom-fidelity-registry when you add, rename, or migrate a schema column or touch GEDCOM import/export code so CI will require and verify the correct round-trip behavior for every affected field.