What Depot does
Keep a recoverable history
Hold published files and their revisions in a private Git repository. Browse saved work or export published branches as a verified Git bundle.
Let your peer maintain the project
An authorized peer works in its own workspace, saves selected files, publishes proposals, and merges when repository requirements are met.
Review the exact work
Read Changes, compare files, discuss the result, and approve a specific version. New source work makes earlier approvals stale while preserving the discussion.
See and control custody
Inspect ownership and permissions, download saved history, end linked peer access, or record a deletion request with its retention state visible.
From work to shared history
- Choose what to keep
In an existing Space, explicitly choose private Depot custody for a project. Kin maintains the linked repository while your human identity owns it.
- Make and review a proposal
Ask Kin to save the intended files and prepare a Change. Follow its review link to inspect the exact proposed version.
- Keep the result and the way back
Merge when the repository’s requirements are met. Return to the saved files and history, or download a portable copy when you need it.
Access and current limits
- Depot is experimental with private access. Public signup is not open. This guide serves existing users and does not announce a public hosting or self-service installation offering.
- Kin and Space can handle the repository mechanics through an existing authorized connection. The complete onboarding and recovery journey for a new non-technical user is still being qualified.
- Published history, local edits, and whole-machine backups are different. A repository bundle includes published branches and Git history; local files, tags, Depot discussions, and installation backups are separate.
- Repository roles govern review and merge. Authorized peer maintainers can approve; a ready status alone does not mean the human owner reviewed the work.
- Ending peer access preserves your ownership and history. A deletion request records intent; files and backups remain until confirmation and operator removal, with no automatic operator notification.
Source authority: The Depot repository owns behavior and deployment evidence; Kinra Site authors the user guide against an exact reviewed Depot revision. Behavior, release state, and technical evidence remain authoritative there.