Glossary
Accepted. A commit that has passed validation and is permanently part of a repository’s history. Acceptance is the point of no return. See System design.
Activation. Making a complete repository the writer that succeeds a
retired source, with synck repository activate --source-retired. Its
authority becomes LOCAL. See Taking over as the
writer.
Archive. A verified backup copy, made with synck archive or synck repository archive. It is another complete repository, without a checkout.
Author. The name recorded on a commit for attribution. It is a label, not an authenticated identity.
Authority. The single writer that accepts an item’s changes and orders
them. A complete repository records its local authority as FOLLOWER,
INDEPENDENT_LOCAL or LOCAL.
base_seq. The item sequence a change was based on. If the item has moved
on since, the change is rejected as stale instead of overwriting newer work.
Blob. The stored bytes of one file version, identified by sha256:
followed by the SHA-256 of the bytes. In output, a file’s blob_id.
Body. The stored text of a message, comment or post. Encoded with a fixed header and a random salt. See How a body is encoded.
Checkout. A repository’s files and folders written to disk for editing.
synck init creates a repository with one, and synck repository checkout
adds one to a copy. Its authority becomes INDEPENDENT_LOCAL. A partial
checkout includes only selected paths.
Checkpoint. A sealed repository sequence, used with --through to read a
repository as it was at that point.
Chunked storage. The default storage layout, which splits content into
compressed, deduplicated chunks, many stored as deltas, in
.synck/object-store.sqlite3. See Storage
space.
Clone. Another working tree of a repository on the same machine, made with
synck clone. It commits into the origin’s history, and synck pull brings in
the commits of the other working trees. A held clone keeps its commits until
synck push. See Clones and
alternatives.
Closure. The complete set of content and metadata objects that a repository’s retained history refers to: every file version, body and attachment, including those of trashed and deleted items. A complete repository contains its whole closure.
Commit. A group of one or more events accepted atomically, with an author, an optional message and a content-addressed ID. Commits name no parent.
Commit ID. The SHA-256 of a commit’s canonical header, which includes a hash of its events. See Commit identity.
Committer. The tool or service that recorded a commit, kept separate from its author. Part of the commit ID.
Complete repository. A self-contained repository, format 7, holding the
entire retained history of every item type and its whole closure. Every Synck
repository is complete, whether created with synck init, exported or copied.
See Complete repositories.
Conflict. A file changed both in a working tree and in history. synck pull merges text files with conflict markers and keeps the repository’s
version of any other file beside it, and synck resolve marks each one done.
Duplicate. A copy of a committed file or folder, made with synck duplicate, that records which revision it began as. An alternative to work
on and later synck adopt.
Event. One recorded change to one item, such as FILE::SET_CONTENT or
CHAT::MESSAGE::CREATE, stored in canonical JSON.
Finalize. Completing the follow-up work for a write that was accepted but
reported that it needs recovery, with synck repository finalize.
Follower. A complete repository that can be read, verified and copied, but not changed. Every export and copy starts as a follower.
History index. Derived snapshots of repository state at each sealed
position, for fast reads of the past, kept in a cache beside the history. It
can be rebuilt with synck fsck --rebuild-state-index.
Item. Anything with a permanent identity and its own history: a file, folder, chat, email, task list, calendar and so on. Every item is either a tree item or a record.
Item ID. An item’s permanent identifier, a UUIDv7. It survives renames and moves.
Item sequence (item_seq). An event’s position in its own item’s history.
Used to select file versions with --item-seq.
Key. An optional, fixed string that makes a record unique: at most one live record of a type has a given key.
Lifecycle. An item’s state: LIVE, TRASH (deleted and recoverable) or
TOMBSTONED (final). History is kept in every state.
Link. A record’s optional filing in one folder. A link has no name or
path, and a checkout ignores it. synck item list --records --parent FOLDER
lists the records linked to a folder.
Metadata. Small JSON objects that events refer to, such as a file’s size or a chat’s title, stored salted in the history database.
Named version. A label on one version of a file, such as 1.00, with a
kind (major or minor) and optional description. Stored in the file’s ref
ledger. See Named versions.
Profile. The rules that turn an operation on a family of items into canonical events, such as the FILE/FOLDER profile.
Publish. Installing a finished, verified output, such as a copy or an extracted file, at its destination.
Record. Any item that is not a file, folder or federated mount: a chat, email, post, task, task list, calendar, call, contact and so on. A record has no name, parent or path, and is never written to disk; people see its title. It can have a key and a link. See Tree items and records.
Ref ledger. A second history attached to an item, with its own ref_seq,
for changes about the item rather than to it, such as named versions.
Repository. A directory with a .synck directory inside, holding history
and content, with or without a checkout.
Reservation. A path claimed with synck lock acquire, so that commits to
it from any working tree need the reservation’s token. It expires unless
renewed.
Repository sequence (repo_seq). A commit’s position in a repository’s
overall history, assigned after acceptance. Positions have no gaps.
Salt. Random bytes stored with each body and metadata object so that identical texts get different IDs. Not encryption.
Sealed. An accepted commit that has been given its repository sequence.
Sequencer. The step that assigns repository sequences to accepted commits, in an order that readers can scan without skipping anything.
Subitem. A record inside an item’s history that is not an item of its own, such as a chat message, a reaction or an attachment.
Trash. Where deleted items go. synck deleted lists them, and
synck recover brings them back with their identity.
Tree item. An item with a place in the folder tree: a folder, a file or a federated mount. It has a name, a parent folder (or sits at the top) and a path. A checkout writes files and folders to disk.
Verification. Rechecking a repository’s history and content against their
hashes and rules, with synck fsck or synck repository verify.
Whole-file storage. A storage layout that keeps every file version and
body as one plain file in .synck/objects/, named by the SHA-256 of its
stored bytes.
Working tree. The files and folders of a checkout or clone, as they are on
disk right now. synck status compares it with the latest commit.
Workspace. In SynckHub, a workspace (also called a case, matter, deal, project or engagement) is a folder that organizes a project. Its role is recorded in its own history, and chats, email and other records can be filed in it by a link. See Workspaces.