Shared primitives

Everlock's architecture is built on a small set of reusable primitives. These are not optional conveniences; they are the common foundation that backend families are expected to reuse.

Versioned storage

Git-backed storage for mutable records that benefit from history and auditability. This is the right fit for content repositories, configuration-like state, and similar data. Every write is a Git commit; every store is a bare Git repository accessible through backend-git-ssh.

See Versioned storage for the full technical explanation and access patterns.

User

A shared identity model for principals, groups, credentials, and access paths. Frontends resolve credentials; backends enforce domain-specific authorization using the shared model.

Jobs

An async scheduler for background work such as index rebuilds, previews, and other derived tasks.

Why this matters publicly

Without these primitives, every backend would drift into its own identity and persistence scheme. With them, contributors can reason about the project as one system instead of many unrelated services.