Architecture
One semantic graph, projected wherever you work.
Available now, public alpha
Kin stores software entities and their relationships in a repository graph. Files, diffs, editor views, and agent tools remain usable as ways to read and work with that graph.
The model
Structure is stored once, then served through focused surfaces.
The graph holds named code entities and relationships. Each surface asks the same authority for the view it needs.
Repository graph
Stores semantic entities, relationships, snapshots, and the evidence needed by Kin workflows.
Developer surfaces
The CLI, daemon, MCP server, editor, and supported projections query or materialize that graph.
Team surface
KinLab adds hosted collaboration and shared memory without redefining the local repository model.
Adoption today
Kin works beside Git.
Teams can adopt the graph without replacing every current workflow at once. Compatibility paths help migration, while the graph remains the semantic authority inside Kin.
Git coexistence is available today. A complete replacement for every Git workflow is not being claimed.
Next step
See the model in a real repository.
Install Kin and query the graph through the CLI or your agent.