Linus Torvalds

Source: https://influences.sgit.ai/register/torvalds/index.html↗ · markdown twin of the entry page.

An influence on Dinis Cruz — one of 25 entries in his register.

• tier traced — corpus evidence exists today
• kind person
• status full — the seven-block register format
• briefing none

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

• anchor: https://git-scm.com/ ↗

Two works, unusually — the entry is about what they have in common rather than about either.

Linked, never rehosted.

Block 2 — In his own words

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

• 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

• Git — the tool, and its own history — worth reading how fast it was written and why https://git-scm.com/ ↗
• 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 https://www.youtube.com/watch?v=4XpnKHJAok8 ↗

The corpus evidence

CC BY 4.0 — Dinis Cruz, with AI co-authorship (Claude, Anthropic). The anchor work belongs to its author and is linked, not licensed here.