# Part of the sgit.ai network

> Where this site sits among the sibling sites on *.sgit.ai, which question it owns, and the deconfliction rule that keeps it from restating what a sister site already argues better.

*Source: <https://myfeeds.sgit.ai/network/index.html> · site v0.1.2 · 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.*

---

Provenance

# Part of the sgit.ai network

A family of focused sites on `*.sgit.ai` subdomains, each taking one question further than a section on the main site could. They share a design, a discipline — sourced claims, a stated status, honest edges — and the convention of publishing an argument before the thing it argues for.

## The question this site owns

Who should hold the record of what you read?

Everything here follows from that one question, and anything that does not follow from it belongs on a sibling site instead. That is the deconfliction rule, and it is the practical reason the network exists: nineteen sites each answering one question is legible, and one site answering nineteen is not.

| Question | Belongs to |
|---|---|
| Who should hold the record of what you read? | **This site** |
| What is an encrypted vault, and how does version control work on one? | [sgit.ai ↗](https://sgit.ai/) |
| How do you compose a team of agents with more than one role? | [teams.sgit.ai ↗](https://teams.sgit.ai/) |
| How do you keep issues in the repository they track, as files? | [issues-fs.sgit.ai ↗](https://issues-fs.sgit.ai/) |
| How should an app call a language model without holding an API key? | [llms.sgit.ai ↗](https://llms.sgit.ai/) |

## What this site inherits rather than invents

- **The vault, and its security model.** Client-side encryption, branches and merges, a read key that is a complete credential. Owned and documented at [sgit.ai](https://sgit.ai/security/index.md); summarised here only where a reader needs it, and marked unverified where this site is repeating rather than checking.

- **Roles as files.** The `ROLE.md` format, the exclusion list that makes a role a role, and the finding that a Central Claim should be written as a failure condition — all measured and argued at [teams.sgit.ai](https://teams.sgit.ai/role-format/index.html). This site applies it; it does not re-derive it.

- **Issues as files in the repository.** The board here is the smallest useful version of the argument made at length by [issues-fs.sgit.ai](https://issues-fs.sgit.ai/).

- **Publishing before building.** The estate convention that a commitment published early is checkable later, applied most visibly by [pki.sgit.ai](https://pki.sgit.ai/), which published its registry's design before the registry existed.

## Corrections go upstream

The network directory on sgit.ai carries one entry per sibling site, written in that site's own words, and a sibling corrects the directory when it is wrong about it rather than the other way round. This site does not appear in that directory yet — [card 005](../team/board.md#todo) is open to send the entry.

**Corrected in v0.1.2.** Until this release the paragraph above ended “until it closes the network is, from the outside, correct not to list a site that serves nothing.” That was true when it was written and stopped being true the moment v0.1.1 deployed: `myfeeds.sgit.ai` now serves. The entry is still unsent, which is a card, not an excuse.

[The full network ↗](https://sgit.ai/network/index.html) [About this site →](../about/index.md) [← Home](../index.md)

---

*[Site index for agents](../llms.txt) · [HTML version](https://myfeeds.sgit.ai/network/index.html)*