myfeeds.sgit.ai / Provenance

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.

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; 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. 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.
• Publishing before building. The estate convention that a commitment published early is checkable later, applied most visibly by 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 is open to send the entry.