persistencelisted
Install: claude install-skill wntic/pyhouse
# Persistence — the store-generic obligations
The obligations every program meets where it keeps data in a store, whatever its architecture family
and whatever the store. Each is stated so that it survives a change of driver, store or family; none
binds a library. The file that satisfies them — a table, a repository class, a revision — is written
under the project's own data-access skill: the architecture family's where one is installed, the
project's own layout where none is. **Which identifier a new row gets is not here**: the identity
scheme is the family's, because the two families answer it differently for reasons of their own.
## When to use vs. neighbours
- A flat-layered service's data-access package, its tables, its repository classes and where its
migration history lives → `flat-persistence`, in the `pyhouse-flat` plugin, which binds these rules
to one stack.
- A hexagonal service's relational adapter behind a port, its paired revision and its unit of work →
`hex-persistence`, in the `pyhouse-hex` plugin; an aggregate on a key-value or document store →
`hex-store-repository`, in the same plugin.
- The error classes a translation produces, translation with the cause chained, the mandatory
fallback, and what `context` may and may not carry → `exception-catalog`.
- Which scope logs a failure the data-access code raised, and the event a success earns →
`python-logging`.
- The declared type a row is mapped into, and which builtin holds an instant, an ident