Documentation, sgit
sgit documentation: quickstart, concepts, guides for humans and AI agents, and the honest limitations page.
Source: https://sgit.ai/docs/index.html↗ · site v0.6.8 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a .md twin; internal links below point at them.
Documentation
Start with the five-minute quickstart. If you know git, the Rosetta stone will make sgit feel familiar in one read.
Introduction
What is sgitThe pitch, the mechanism, the architecture↗ Installationpip install, verify, upgrade↗ QuickstartCreate, commit, push, clone, in 5 minutes↗
Concepts
sgit for git usersThe Rosetta stone: same verbs, three differences↗ The two-branch modelClone branches, named branches, and why↗ The security modelWhat the server sees; the crypto stack↗ Vault credentialsRead keys, vault keys, and what each prefix declares↗ Keys and signaturesEncrypting to someone who holds no vault key↗ Performance, cost and running everywhereNo live database, LETS, and what a read actually costs, measured↗
Messaging & the API
Sending messages between vaultsAppend lanes + PKI, composed into a worked example↗ The HTTP APIEndpoints, headers, gates, limits and error codes↗ Append lanesThe write-only transport behind vault messaging↗
Guides
Working on a vault: start hereThe practices that get repeated most, and where each answer lives↗ Three surfaces_page.json, a vault app, or a site page, pick this first↗ Working with AI agentswrite, --json, sparse clones, multi-agent patterns↗ Use casesFive workflows, all on shipped commands↗ SG/Vault platformThe browser app, vault apps, the window.sg bridge↗
Project
When NOT to use sgitThe honest page↗ Why does this exist?Answering the no-market criticism, plus a FAQ↗ If a vault key is exposedThe rotation runbook, with a real case study↗ Cross-team briefsOpen asks to the CLI and API teams↗ Admin & engineeringHow this site is built and released↗ GitHubSource, issues, changelog ↗
Coming next: a full per-command CLI reference, generated directly from the CLI's own argument parser on every release, so the reference can never drift from the shipped tool.