The vocabulary of git-native tracking
grite lives in the world of CRDTs, event logs, and git internals. If some terms on the how-it-works page were new, here they are in plain language.
- CRDT
- Conflict-free replicated data type. A data structure that can be replicated across machines and merged in any order to the same result. grite uses CRDT rules so concurrent issue edits never conflict.
- Event sourcing
- A pattern where state is derived by replaying an ordered log of change events rather than storing the current state directly. grite is event-sourced: the WAL is truth, and issue state is projected from it.
- Append-only log
- A log that is only ever added to, never edited in place. grite's WAL is append-only, which makes history immutable and always reconstructable.
- Git ref
- A named pointer to a commit or object inside a git repository (like a branch or tag). grite stores its data under a dedicated ref so it rides along with your repo.
- refs/grite/wal
- The specific git ref where grite keeps its write-ahead log of issue events. It lives inside your repository and syncs through the same remote as your code.
- WAL (write-ahead log)
- The append-only sequence of events grite records for every issue mutation. It is the single source of truth from which all issue state is derived.
- CBOR
- Concise Binary Object Representation — a compact, self-describing binary serialisation format. grite encodes each event as CBOR so the WAL stays small and fast to decode.
- Ed25519
- A fast, modern public-key signature scheme. grite can sign each event with a per-actor Ed25519 key, giving non-repudiable provenance for who made each change.
- Deterministic merge
- A merge whose result depends only on the inputs, never on the order of operations. grite's CRDT merge is deterministic, so every clone converges to the same issue state.
- Content-addressed
- Identifying data by a hash of its contents rather than by location. grite's events are content-addressed, so any tampering breaks the hash chain and is detectable.
- Daemon (grite-daemon)
- An optional background process that keeps grite's projected issue state warm and serialises concurrent CLI calls. It is a performance optimisation; the CLI works without it.
- Repo-local
- Living inside the repository itself rather than in an external service. grite is repo-local: clone the repo and you have the full issue history, offline.