Simon Wardley & Wardley Maps
The deepest-traced influence in the corpus by volume — around 210 files — and the one whose material is entirely a sibling site's. This entry owns only the resonance: why a security person reorganised his thinking around an evolution axis.
Block 1 The anchor
Wardley Maps — Simon Wardley
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 book/blog series, published in the open. The anchor is the mapping method itself rather than any single post.
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 resonance is not the diagrams. It is that mapping makes a strategy arguable: two people looking at the same map can disagree about where a component sits and settle it with evidence, which is impossible when the strategy is a paragraph of prose.
That is also why this influence keeps appearing in places that have nothing to do with strategy. The evolution axis is a claim about a component's state; the risks register's accepted-risk format is a claim with a named acceptor; a trace row on this site is a claim about a codebase. The shape is the same, and it came from here. Popper is the other half of that story.
Block 3 The principle
Situational awareness before strategy — draw the map before you argue about the move, and the map is a falsifiable claim about position and movement rather than a picture of your opinions.
Block 4 The trace table
The trace of this influence is an entire site. Reproducing it here would break the deconfliction rule the network runs on: two sites making the same argument slightly differently is worse than a dead link. The influence entry owns the resonance; the sibling owns the material — the maps, the evolution axes, the maps-as-code work and its own release history.
↗ wardley-maps.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.
- Is the map drawn before the strategy is argued, or produced afterwards to justify it?
- Does every component on it sit somewhere on the evolution axis, or are some of them just boxes?
- Is the claim about movement — where this is going — or only about where it is now?
- Could someone who disagrees point at the specific thing they think is misplaced?
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/.
- Wardley Maps (the online book) — the whole method, published free by its author ↗
- Learn Wardley Mapping — the community's structured entry point ↗
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 |
|---|---|
(corpus-wide, ~210 files) | the largest single-influence footprint the mining run found, spanning strategy documents, briefs and the published mapping material |
wardley-maps.sgit.ai (sibling site + its own brief pack) | Dinis Cruz's own published Wardley material — videos, infographics and the maps-as-code work |
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
- Sibling site: wardley-maps.sgit.ai — the maps, the evolution axes, the maps-as-code work, and Dinis Cruz's own published mapping material