-
Notifications
You must be signed in to change notification settings - Fork 0
GEDCOM_COMPATIBILITY
The supported GEDCOM and RootsMagic command syntax is maintained in the CLI reference. RootsMagic export supports portable and preservation profiles, connected/ancestor/descendant scopes, optional generation limits, and GEDCOM 5.5.5 with a deliberate 5.5.1 fallback.
The internal characterization CLI still recognizes --quality-report,
--no-quality-report, --quality-root-person, and --quality-ai; application
callers should use the service and unified command options documented by
ancestry --help.
The merge engine preserves custom/vendor structures, citations, conflicting facts, family links, and stable pointers whenever representable. Optional LLM adjudication may identify likely duplicates but cannot delete conflicting evidence. Incremental sync never automatically deletes people, relationships, cited facts, protected baseline/manual content, families, or sources.
The safe offline fixture demo uses quality-source-a.ged,
quality-source-b.ged, and root Maren Hollow:
scripts/gedcom_merge_quickstart.sh --skip-installBefore claiming a release interoperable, record automated validation and manual imports into current Ancestry, Geni, and MyHeritage products for both 5.5.5 and any advertised 5.5.1 fallback. Verify root selection, people/family counts, citations, names, dates, living-person behavior, and custom-tag loss reports.
- Home
- CLI reference
- Interactive console guide
- Architecture ownership and dependency contracts
- Bounded file ingress
- Versioning and compatibility
- Continuous integration
- Release runbook
- Encrypted backup and recovery
- First-run storage diagnostics
- GEDCOM compatibility and release checks
- Built-in module authoring
- Privacy and consent
- Provider guide
- Local LLM benchmarks
- Local-first retrieval evaluation
- Wiki synchronization
- Wiki operations and recovery
- Security response checklist
- Electron and FastAPI desktop ADR
- Data-flow threat model and control matrix