Open source & its licences
A link-out entry that owns one thing the sibling site does not foreground: open source as personal formation. What two decades of releasing tools taught about licences as social contracts rather than legal ones.
Block 1 The anchor
Releasing tools in the open, from the O2 Platform era onward
No canonical URL. Not every anchor has one address — a book, a practice or a personal era does not — and this site links what is linkable rather than inventing a canonical home for something that has none. The wider library below carries what can be linked.
A practice rather than a work. The anchor is the habit of publishing, and what it cost and returned.
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.
The sibling site carries the history, the licence positions and the argument for publishing. What belongs here instead is the formation: what releasing changes about how you write. Code you will publish is code you explain; a tool with users is a tool with a boundary; and a licence choice made twenty years ago still decides who can use the thing today.
The second strand is the one that connects to the rest of this register. Open source is the demonstration that OWASP's compounding-in-the-open claim works outside a conference, that Raymond's essay described something real, and that Torvalds built the two pieces of infrastructure the whole habit now rests on.
Block 3 The principle
Releasing work is how it compounds — and the licence is the constitution, not the paperwork: it decides who can build on this and what they owe.
Block 4 The trace table
The trace of this influence is an entire site, with a full history pack behind it. This entry owns the personal half — what publishing did to Dinis Cruz's practice — and two nested entries: The Cathedral and the Bazaar and Torvalds.
↗ open-source.sgit.aiBlock 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.
- If this were public tomorrow, what would have to change first — and is that thing a defect?
- Does the licence say what someone building on this owes, or only what they may not do?
- Is the boundary of this tool something a stranger could find, or only something the author knows?
- Is this being kept private for a reason that would survive being written down?
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 |
|---|---|
open-source.sgit.ai (sibling site + its brief pack) | an 11,619-word corpus and a 17,909-word history on file — the material this entry deliberately does not repeat |
(corpus-wide) | licence positions and publishing decisions across the estate |
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
- Nested here: The Cathedral and the Bazaar
- Nested here: Linus Torvalds
- Sibling site: open-source.sgit.ai — the licences, the packages, the history pack, and the argument for publishing