0.3.0

AncestryLLM 0.3.0

AncestryLLM 0.3.0 establishes one framework-independent genealogy kernel and one application-service layer for the existing ancestry terminal surfaces and future adapters.

Highlights

• One shared CommandSpec inventory and immutable CommandExecutor registry now drive both one-shot CLI and prompt-toolkit/Rich REPL dispatch.
• Transport-neutral invocations, outcomes, operation DTOs, ports, opaque artifact references, and stable error envelopes form the application boundary.
• A service-owned genealogy aggregate defines canonical identity, provenance, deterministic change/conflict accounting, and quality findings.
• GEDCOM merge, subtree, quality, incremental update, and rebase services expose deterministic result contracts without depending on terminal, web, desktop, provider-SDK, or host-filesystem types.
• FastAPI and Electron remain unimplemented later-roadmap adapters. They must consume the same application surface and may not redefine command or domain behavior.

Preserved compatibility and safety

The 0.2.0 one-shot CLI and interactive-console grammar remains supported, including --json, stable coded errors, explicit remote-provider selection and consent, and network-free provider=none. RootsMagic inputs remain immutable, GEDCOM transformations remain rooted and loss-minimal, and staged output, report, manifest, encrypted-backup, cancellation, and complete-or-rollback contracts remain regression-tested.

Verified release guarantees

Publication is gated on the attached release-evidence.md. A verified gate means the exact release commit passed the documented test, static-analysis, security, reproducibility, clean-install, and hosted-control checks. The wheel and source distribution must have identical hashes to the approved readiness build before publication proceeds.

The release workflow verifies installation on Ubuntu, macOS, and Windows with Python 3.12, 3.13, and 3.14. For an index-backed release, it also verifies that the PyPI and TestPyPI files match the attached distribution hashes. If an index is unavailable and the release is published on GitHub only, the GitHub Release body states that limitation explicitly and no index-verification claim applies.

Interoperability limitations

RootsMagic, Ancestry, Geni, and MyHeritage interoperability is unverified for 0.3.0 unless a corresponding row in the attached evidence is explicitly marked verified with dated fictional-data evidence. This release does not make a positive compatibility claim for an unverified vendor. Automated tests verify standards-based GEDCOM formatting, deterministic preservation, and immutable RootsMagic handling only.

Installation

Install the isolated CLI application with:

pipx install ancestryllm==0.3.0

If the release body identifies a GitHub-only publication because PyPI was unavailable, download the attached wheel and install that exact file instead:

pipx install ./ancestryllm-0.3.0-py3-none-any.whl

Then verify the installed public version:

ancestry --version
python -m ancestryllm --version

Both commands return ancestry 0.3.0.

Release assets and verification

The GitHub Release contains the wheel, source distribution, full SHA256SUMS, CycloneDX SBOM, security-finding dispositions, interoperability record, readiness evidence, and final release evidence. GitHub build provenance binds the assets to the release workflow and commit. An index-backed publication also includes PyPI Trusted Publishing attestations for the Python distributions.

Verify all downloaded GitHub assets from the directory containing them:

shasum -a 256 -c SHA256SUMS

SHA256SUMS intentionally omits only itself.

Upgrade and correction policy

Published artifacts and v0.3.0 are immutable. If a defect requires a correction, the project will publish a new patch version rather than replacing this tag or version. The 0.2.0 tag, release, notes, and evidence remain unchanged.