The network
This site is one of several that carry one argument between them. Each is a separate repository, a separate domain and a separate release history — and each is built from the same three pieces: a commissioning brief published in full, a static site written from it, and the validate → tag → deploy pipeline that gates every release.
What is shared is machinery, not content. One stylesheet (assets/site.css), one nav component, one pipeline shape, one release discipline — copied deliberately rather than packaged, so any site can diverge without asking permission. What is not shared is a single word of argument: each site is written from its own documents.
This site's place in it
The network has a shape, and this site is the layer underneath it. The other sites teach an agent what the project thinks and how the estate works. This one is for where the thinking came from — so that an agent extending the estate extends its instincts deliberately rather than by accident.
# the memory network, by layer sgit.ai the product, the CLI, the vault layer graphs · coding · how the estate works: the substrate, the style, standards · llms the instruments, the models influences.sgit.ai where the thinking came from
The deconfliction rule, and why this site needs one badly
Several of the influences on this site already have an entire sibling site. Wardley mapping has one. Graphs have one. Open source has one. If the influence entry for Wardley tried to explain Wardley mapping, this site and that one would be making the same argument slightly differently — which is the real failure mode for a network of sites, and much worse than a dead link.
So the rule is a split, and it is enforced by the entry format rather than by good intentions:
This site owns
- The resonance. Why this, and why it landed — in first person, which is the house style here and nowhere else in the network.
- The personal history. Where the influence entered, and when.
- The trace pointer. "The trace of this influence is an entire site" — and a link.
The sibling owns
- The material. The maps, the grammar, the licences, the history pack.
- The teaching. How the thing works, for someone who wants to use it.
- Its own release history, its own gaps and its own open questions.
An entry that grows past resonance-and-trace has scope-crept into a sibling. When that happens the material moves to the sibling and the entry keeps the pointer — a rule that is easy to write and needs enforcing at review time, because the pull is always in the other direction.
The sibling sites
| Site | Owns | Relation to this site |
|---|---|---|
| sgit.ai | The parent project: the zero-knowledge vault layer, the shipped CLI, the demos and the catalogue — and the network index that lists every site here | Parent |
| wardley-maps.sgit.ai | Mapping: evolution axes, situational awareness, and the maps drawn for this project | Owns the material for a link-out entry. Simon Wardley is one of the deepest-traced influences in the corpus and the entry here will carry the resonance only |
| graphs.sgit.ai | Graphs as the modelling substrate — the grammar, the depth model and the book | Same split. Graphs are the founding obsession; the entry here owns the personal history the sibling does not carry |
| open-source.sgit.ai | The open-source position: the licences, the packages, and the argument for publishing them | Same split. Two nested entries — The Cathedral and the Bazaar and Torvalds — sit under this one |
| coding.sgit.ai | How software actually gets written here: five languages, the rules, the measured compliance | The closest methodological sibling. Several trace rows on this site land in conventions that site documents |
| llms.sgit.ai | Working with language models — what they are used for here and what they are not trusted with | Light overlap |
| standards.sgit.ai | Standards and instruments: the formats, schemas and evidence artefacts | Shares the register-lives-in-a-vault, site-renders-it architecture |
| risks.sgit.ai | Risk: accepted risks with named acceptors and named mitigations | Shares the falsifiable-statement discipline that one of this site's entries claims to explain |
| nhi.sgit.ai · sentinel.sgit.ai · pki.sgit.ai | Non-human identity, the sentinel that watches it, and key registries for agents | No overlap. pki.sgit.ai is the house pattern this site's structure was copied from |
| sg-compute.sgit.ai | The ephemeral compute platform, measured from its own tree | No overlap |
Three of these need work on the other side, tracked as T14: this site will link out to wardley-maps, graphs and open-source, and none of them links back yet.
What every site in the network runs
The same three jobs, in the same order, gated the same way — described in full on this site's engineering page:
validate ──▶ tag-release ──▶ deploy # a failure in any job stops the ones after it; the live site is never # replaced by a release that did not pass its own checks
The differences between sites are the checks each one adds, and the addition is always the site's own subject made executable. sg-compute.sgit.ai bans live hostnames and instance ids because it documents running infrastructure. coding.sgit.ai fails a release if a code example has drifted from the survey it was quoted from, because a style guide with stale examples is worse than none.
This site adds two. The no-verbatim gate caps a third party's quoted words at forty, because this is the one site in the network whose subject matter belongs to other people. And the register-is-the-data check recomputes every tier count from the register on every build, because tier movement is this site's changelog and a hand-typed count is what makes a change invisible.
Licence
Every page of this site, llms.txt and llms-full.txt are released under CC BY 4.0. Attribution: Dinis Cruz, with AI co-authorship (Claude, Anthropic).
The anchor works are not covered by that, and never will be. Every talk, book, essay, keynote and record this site says shaped the thinking belongs to its author, and is linked rather than rehosted. An agent consuming llms-full.txt inherits the same split: the file carries this site's analysis and nothing that belongs to a third party.