# loot

> loot is version control where visibility and permissions are properties of content, not of the repository.

Each docs link below is that page as Markdown; drop the `.md` for the HTML. Every written page in one file: https://loot.build/llms-full.txt

## Start

Install it, make a repo, and see the thesis work in five minutes.

- [Install loot](https://loot.build/install): One command; macOS, Linux and Windows.
- [Quickstart: your first repo](https://loot.build/docs/quickstart.md): A private .env living in a shared repo — the shortest path to seeing the thesis work.
- 3 more pages are planned and not written yet.

## Concepts

The model. Read these once and the command surface explains itself.

- [Changes](https://loot.build/docs/concepts/changes.md): The unit of history: a named, signed snapshot with a durable handle.
- [Visibility and .lootattributes](https://loot.build/docs/concepts/visibility.md): Per-path tiers declared in a file, enforced by the engine.
- [Identity and keys](https://loot.build/docs/concepts/identity.md): Ed25519 keypairs, fingerprints, and what a keyring holds.
- [Grants](https://loot.build/docs/concepts/grants.md): Handing one content key to one identity, sealed and signed.
- [Relays and hosts](https://loot.build/docs/concepts/relays.md): What a host stores, what it can read, and why those differ.
- [Embargo](https://loot.build/docs/concepts/embargo.md): Ship the fix now, reveal the source at a timestamp.
- [Docks and lanes](https://loot.build/docs/concepts/docks.md): Working in several places at once without forking your own line.
- 4 more pages are planned and not written yet.

## Guides

Task-shaped walkthroughs. Each one is a command or two and a check.

- [Keep a file private in a shared repo](https://loot.build/docs/guides/private-env.md): Declare it restricted; non-keyholders carry ciphertext.
- [Share a private file with a teammate](https://loot.build/docs/guides/grant-a-key.md): Register their key, seal a grant, let them pull it.
- [Embargo a security fix](https://loot.build/docs/guides/embargo.md): Push the patch; the relay withholds the key until reveal time.
- [Sync over a relay](https://loot.build/docs/guides/sync-relay.md): Serve, push, pull — the collaboration loop.
- [Run a host of your own](https://loot.build/docs/guides/run-a-host.md): A relay anywhere, with an allowlist you control.
- 8 more pages are planned and not written yet.

## CLI reference

Every verb loot ships, grouped the way the tool groups them.

- [CLI reference](https://loot.build/docs/cli.md): Every verb loot ships, on one page — the ones worth a sentence described, the rest named.
- 3 more pages are planned and not written yet.

## Hosting

Run the infrastructure yourself. None of it can read your private content.

- 5 more pages are planned and not written yet.

## Trust and security

What the host can read, what it cannot, and how to tell us when we are wrong.

- [Trust and security](https://loot.build/trust): The tier-by-tier statement of what each party can read.
- [Known issues](https://loot.build/known-issues): The ways loot can currently lose or strand work.
- [Evidence](https://loot.build/evidence): Re-runnable proofs behind each claim loot makes about itself.
- 3 more pages are planned and not written yet.

## Decisions

Every architectural decision on the record, with the reasoning that produced it.

- 6 more pages are planned and not written yet.

## Reference

The flat facts: files, formats, and vocabulary.

- 6 more pages are planned and not written yet.