Commits and history
A commit records a local project state and its parent relationship, giving large assets the same navigable history shape users expect from source control.
Snapshot, not folder naming
A commit connects paths to exact recorded content and metadata. A parent relationship creates history without relying on names such as final-final-v3.
Staging
dits add chooses which working-tree changes belong in the next snapshot. dits status and dits diff help inspect that boundary before committing.
History operations
Local log, show, diff, checkout, reset, restore, reflog, blame, bisect, rebase, cherry-pick, stash, tag, branch, and merge paths exist in the alpha. Individual edge cases are governed by the generated CLI reference and current tests rather than a blanket Git-parity guarantee.
Authorship and trust
Commit metadata can record an author, but a name string is not verified identity. Signed authorship, remote authorization, policy enforcement, and multi-user audit remain separate future concerns.
Semantic history
The research direction adds explicit edit, dependency, and rendition records to a commit graph. Those records must remain traceable to exact source and are experimental today.