-
Notifications
You must be signed in to change notification settings - Fork 0
README
github-actions[bot] edited this page Jul 25, 2026
·
2 revisions
Each release workflow produces an immutable evidence bundle attached to its GitHub Release. The bundle identifies the semantic version, signed tag, commit, workflow run, artifact hashes, supported platform/Python matrix, SBOM, quality gates, security finding dispositions, and GEDCOM importer status.
Release evidence contains fictional or aggregate test data only. It must never contain genealogy payloads, credentials, databases, backups, local paths, logs, prompt/response bodies, or secret values.
A gate is recorded as verified, failed, unavailable, or unverified.
Only verified supports a positive compatibility claim. unavailable and
unverified remain visible limitations in the release notes.
- 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