influences.sgit.ai / register / OWASP & the security community

OWASP & the security community

traced community + era full

An influence on Dinis Cruz — entry 5 of 25 in his register.

Not a person and not a work: two decades inside an open community, and the Summit model in particular. The seed list's own phrasing was the cyber security community — an era, treated as an influence in its own right.

Block 1 The anchor

OWASP, and participation in it from the early 2000s onward

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.

The anchor for a community or an era is the first documented contact with it, not a work. The Summits are the specific institution this entry is about.

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 claim worth defending here is narrower than open communities are good. It is about the Summit format specifically: sessions that must produce an artefact, working groups that outlive the room, and outputs published whether or not they are finished. That is an unusual thing to have been formed by, and it shows up in the estate as a set of habits rather than as a topic — publishing unresolved questions as first-class pages, versioning documents rather than replacing them, and treating a working document as a deliverable.

The second strand is what a global, volunteer, chapter-based organisation teaches about distributed work — a lesson learned twenty years before it became a general one, and which nests naturally with diverse and distributed teams.

This entry deliberately does not cover open-source governance or funding models. Those belong to the open-source sibling, which carries the full history pack.

Block 3 The principle

Knowledge compounds fastest in the open, among people who owe each other nothing — and the format of the gathering decides whether it compounds at all.

Block 4 The trace table

No trace table yet. The habits this entry claims — publish unresolved, version rather than replace, treat a working document as a deliverable — are visible across the estate and across this whole site network, and the mining run recorded the volume rather than the instances. Building the rows means naming specific practices and where they are written down, and the entry publishes the claim without them rather than inventing paths to point at. Tracked as R2.

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.

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/.

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 corpusWhat it carries
(corpus-wide, ~271 files)the second-largest footprint in the mining run, including the Summits history
open-source.sgit.ai (sibling site)governance and monetisation material, which this entry links to rather than repeats

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

The whole graph →