Saving with Kin

Kin can maintain your Depot repository while you work together. You decide which work belongs in private custody, what should be saved, and when a proposal is ready for review. The browser lets you inspect the same saved work.

Choose custody before copying work

In an existing Space, use Saving with Depot to create or recover a managed project. Confirm the project and the custody choice. Your human identity owns the linked repository, and Kin receives a maintainer role. Confirm only the files you intend to place there; private custody still copies work from your machine to Depot.

Ask for a small, inspectable result

For example:

Update the project notes, check the result, and save the intended files in Depot. Prepare a Change and give me its review link.

Tell Kin what outcome you want and what should be included. It can work in its own branch, which keeps proposed history separate from the shared version. Ask it to report what was saved, what was published, and what remains local.

Space also has controls for selecting files and saving a checkpoint. Their exact steps belong to the Space guide.

Understand the saved state

State	What it means
Local edits	The files have changed where Kin is working. Depot may not have them.
Local checkpoint	Git history was recorded locally; publication can still be pending.
Published branch	Depot holds those files and their history. They may still be proposed work.
Open Change	A proposal connects published work to the shared version for discussion and review.
Merged Change	The approved proposal has been incorporated into the target branch.

The default Code view can still show the shared version while Kin has saved new work on a proposal branch. Follow the Change link or select the branch to inspect it. Closing your browser is not evidence that a save succeeded.

Review, then continue

Open the review link and follow Reviewing Changes. After the repository’s approval requirements are met, an authorized peer or person can merge. Ask Kin to confirm the merge and bring the resulting shared version back into local work.

If Kin publishes a new source version after review, the old decision remains in history and no longer approves the new work. Review the updated proposal.

When work is interrupted

Ask Kin to inspect the existing operation and repository before starting another save. Space’s Retry saved operation resumes its retained request; use that when offered. If another change has advanced the shared history or a conflict needs a choice, let Kin explain the competing edits before resolving them.

Depot does not monitor a conversation or automatically dispatch a peer when you leave a comment. Return to Kin with the review link and the next instruction.