Linus Torvalds
Builder of two of the things this estate stands on. Nests under open source, and earns a standalone entry for one reason: Git is not just a tool here, it is the shape of an argument Dinis Cruz makes about education.
Block 1 The anchor
Git (2005), and Linux (1991) — Linus Torvalds
Linked, never rehosted. This site explains why the work resonated and traces where it was applied; the work itself stays where its author put it.
Two works, unusually — the entry is about what they have in common rather than about either.
Block 2 In his own words
No first-person statement about this influence exists in the corpus yet. What follows is the site's reading of the evidence, not Dinis Cruz's words — and it stays labelled as such until his briefing document arrives.
Git's interesting property is not distribution, it is that the history is content-addressed and therefore verifiable by anyone holding a copy. Nobody has to trust the server. That is a data-model decision that produced a social one, and it is the same move this estate makes with encrypted vaults: put the guarantee in the structure, not in the operator's promise.
The second strand is why this is an influence rather than a dependency. The corpus's education argument uses Git as its central example — not as a tool students should learn, but as evidence that the way work is recorded determines what can be learned from it. An influence you reach for when arguing about something else entirely is one that has been absorbed.
Kept short deliberately. The governance and community half belongs to the open-source sibling; this entry owns the data-model claim.
Block 3 The principle
Tools that decentralise trust change how people are able to work together — and the change comes from the data model, not from the policy on top of it.
Block 4 The trace table
No trace table yet. The obvious rows — content-addressed history, distributed by default, verifiable without the server — are claims about the estate's vault layer that this repository holds no evidence for. The pack did not record them and this site will not invent them. The rows exist to be written by someone with the repositories open, which is R1.
Block 6 The checklist
What to ask of new work in this influence's light. The checklist is the influence made operational — the part an agent can run without having consumed the anchor work.
- Is the guarantee in the structure, or in someone's promise to behave?
- Could a person holding only their own copy verify that it is the right one?
- If the central server disappeared tomorrow, what would be lost — the coordination, or the work?
- Does the way this is recorded let someone learn from it later, or only let them read the result?
Block 7 The wider library
The rest of the work, linked and never rehosted, each item with one line on what it adds. The full union of every entry's Block 7 is at /library/.
- Git — the tool, and its own history — worth reading how fast it was written and why ↗
- Just for Fun (2001) — Torvalds's own account, and a useful corrective to the mythology
- The 2007 Google Tech Talk on Git — the design argument in his own words, including the parts that have aged badly ↗
The corpus evidence
What the mining run found, by path. These are the files that put this entry in its tier — the claim on this page is checkable against them, which is the whole point of the format.
| Path in the corpus | What it carries |
|---|---|
SGraph-AI__App__Send/team/humans/dinis_cruz/briefs/03/28/v0.19.7__article__education-gaps-git-opensource.md | the Git argument at the centre of the education-gaps article |
(corpus-wide, ~5 files) | Git's history and kernel governance across the open-source history material |
Paths are as recorded by the mining run behind the commissioning pack (v0.33.62, 25 August 2026). This repository holds the website, not the corpus, so they are cited rather than resolved — R2 in the comms queue.
Where this sits
- Nests under Open source & its licences — the governance and community half lives there; this entry owns the data-model claim