Kin and Git
Git keeps a history of your files. Kin is a new way to manage code that also keeps the connections it finds with that history. This page explains the difference and how to try Kin alongside Git.
Both help you track changes. Kin also makes recorded code connections part of what it saves.
Git records file contents and commit history. Other tools can maintain persistent, revision-aware indexes and graphs around that record.
Code, recorded relationships, exact source and change history form the repository. Commits and branches include that structure. People and agents query repository state.
Kin supports Git import and export alongside its native repository operations. Supported editors and build tools still work with ordinary files. Start with a disposable copy of a small, supported repository and the current compatibility guidance.
Kin can miss connections. An empty answer does not prove nothing is connected, so keep checking the source and running your tests.
Unsupported languages remain plain content. Coverage is partial even in supported languages. Some repositories and very large histories are refused before preparation begins.
The practical test is whether the record helps with a real task. Compare useful context, preparation cost and finished-change quality. A different architecture alone does not establish better outcomes.
Public alpha. Coverage and workflow support vary. Compilers, tests and review remain necessary.