Add core data model (12 tables) and initial Alembic migration

All core entities from ARCHITECTURE §5: tenancy (User, Tree, TreeMembership), people (Person, Name, Relationship), facts (Event, Place, PlaceName), provenance (Source, Citation), and the append-only AuditEntry. Cross-cutting mixins give every row a UUID key, timestamps, soft delete, and (where tree-owned) a tree_id for uniform tenant isolation.

Modeling choices: parentage as qualified edges (biological/adoptive/step/foster/donor/guardian) so non-traditional families are first-class; events keep both a verbatim date string and a normalized start/end range; closed sets are PG enums while GEDCOM-extensible vocabularies (event/name/source type) stay strings; CHECK constraints enforce single-subject events and single-target citations. Place is tree-scoped in Phase 0 (see ARCHITECTURE note). The migration is verified reversible (upgrade/downgrade drops tables and enum types) and matches the models (alembic check clean); applied on the deploy target. Dockerfile now ships migrations.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Justin Paul <justin@jpaul.me>

This commit is contained in:

Justin Paul

2026-06-06 10:40:00 -04:00

parent 03124027fe

commit 297cb797d6

18 changed files with 942 additions and 1 deletions

									
										backend/pyproject.toml
									
		+2
		
												View File
												
				@@ -29,6 +29,8 @@ package = false

				[tool.ruff]

				line-length = 100

				target-version = "py313"

				# Alembic writes the migration files; don't hold generated code to our style.

				extend-exclude = ["migrations/versions"]

				[tool.ruff.lint]

				select = ["E", "F", "I", "UP", "B"]