Gitslice docs

Concepts

Gitslice is native source storage first, Git compatibility second. These are the terms that explain how the system works.

Accounts and paths

Every source path starts under a globally unique account slug, such as /nic or /acme. Account kind is metadata, not part of the path.

A slice is a repository-like projection over the global source graph. It defines included paths, visibility, roles, and submit settings.

A workspace is bound to exactly one slice and hydrates the files needed for that scope instead of cloning the whole graph.

A changeset contains one or more patchsets for one authoring slice. Cross-slice changesets are intentionally not supported.

Approvals, checks, path locks, and slice rules are enforced server-side before work is included in main.

Commits exist as immutable accepted snapshots. Users normally create changesets; the system creates a native commit when a changeset lands.

Edit and update patchsets.

Submit accepted and queued.

Included in the accepted main tree.

Immutable snapshot behind refs/global/main.