wardley-maps.sgit.ai / Licensing

CC BY inside a CC BY-SA ecosystem

This site has a licensing problem the other sites in this network do not have, and it shapes real editorial choices rather than sitting in a footer. Saying so plainly is cheaper than hoping nobody notices.

This site publishes CC BY 4.0. The Wardley ecosystem publishes CC BY-SA 4.0. Those are compatible for reading and incompatible for adapting. ShareAlike is viral: quote CC BY-SA material with attribution and nothing happens; adapt it — rewrite, restructure, translate, build a derivative table from it — and the resulting page must itself be CC BY-SA 4.0. You cannot relicense someone else's adaptation as CC BY.

The rule this site follows

CC BY-SA material appears here as clearly-marked quotation and link-out, never as adaptation. Then every page stays CC BY 4.0 and the network's licence stays uniform. That is why the glossary classifies every concept as standard doctrine, extension or original, and why the standard-doctrine ones are linked rather than rewritten. The editorial spine and the licence discipline are the same decision.

Where a page genuinely wants to adapt — a rewritten doctrine list, a restructured climatic-patterns table — the right move is a clearly-marked page carrying its own CC BY-SA 4.0 notice, saying why at the top. One or two such pages are fine. A site with a mixed and unlabelled licence is not. This site currently has none, and if that changes it will be listed here.

Watch the 3.0 / 4.0 split

Simon Wardley's book and most of the ecosystem are CC BY-SA 4.0. His blog, blog.gardeviance.org, is CC BY-SA 3.0. Those are different licences with different notices. Do not merge them into one footer. The PST page cites the blog and carries the 3.0 notice specifically.

The standard attribution string used across the ecosystem, and used here:

Wardley Mapping is provided courtesy of Simon Wardley, CC BY-SA 4.0.

Every resource page carries a per-resource attribution string rather than a generic one, and the screenshot targets file carries the same strings attached to the capture targets — so a screenshot and its credit line cannot drift apart.

What this site's own content is

Everything written for wardley-maps.sgit.ai — every page, /documents/, /briefs/, /llms.txt, /llms-full.txt, the admin surfaces, and the four maps — is CC BY 4.0, consistent with the rest of the network. Every raw markdown document carries the stamp, and the release gate fails the build if one does not, so the stamp cannot quietly drift.

The four maps are original works drawn from this site's own research. They carry no ShareAlike obligation. The technique they use is Wardley's and is credited as such — crediting a technique is courtesy and good practice, not a licence condition, and it is worth being precise about the difference rather than implying an obligation that does not exist.

Four regimes across the resources

RegimeExamplesWhat you may do
CC0awesome-wardley-mapsAnything. No attribution required. The best base for your own list — and the resource this site benefits from most while correcting.
CC BY-SA 4.0The book, all compiled editions, Learn Wardley Mapping's free reference, the Mapping Canvas, wardleymaps.com, WikipediaQuote and screenshot with attribution. Adapt only if you accept CC BY-SA on that page.
CC BY-SA 3.0 ⚠️blog.gardeviance.orgNot 4.0. Separate notice; do not merge.
MIT / AGPLOWM, Mermaid, wardleyToGo, cli-owm, ArcKit (MIT) · the Obsidian plugin and Tranquil's Map (AGPL-3.0)Retain the notice. AGPL's network clause matters if you ever embed one in a service.
All rights reservedLWM's paid course, InfoQ, YouTube, GCATI, the compiled Leanpub book, The Value Flywheel Effect, XebiaBrief quotation and a page screenshot for identification. No re-hosting, no clipping, no reproducing their diagrams.

Six flagged — link only until resolved

Screenshot ethics

  1. A page screenshot for identification is defensible almost everywhere, including all-rights-reserved material — it is how a directory works. Clipping content out of a page is not. No Xebia diagrams, no InfoQ video frames, no GCATI syllabus.
  2. The attribution string travels with the image, rendered under it rather than in a global footer.
  3. The capture record is published — status, title, final URL, timestamp, for successes and failures alike. captured.json. Three captures returned a Cloudflare interstitial rather than the page; those are recorded as blocked and none is published as a screenshot of anything.

Third-party names — where the line is

Fine: naming a technique, a framework, a standard or a tool. Naming Simon Wardley, Ben Mosior, Chris Daniel, Matt Edgar, Danny Buerkli, Damon Skelhorn, Tristan Slominski and the other practitioners in the resource index — they are public authors of public work, credited for it.

Fine: saying MapKeep shut down on 30 May 2026 and crediting Tristan Slominski for building it. That is a factual, sourced obituary and the community needs it recorded.

Not fine: attaching maturity or capability judgements to named commercial competitors, reproducing a vendor cost-scoring table, or naming a private individual as a commercial target.

Never: quoting Discord or forum members without consent.

What is deliberately not published

The corpus this site draws on contains material that is not going to appear here, and the categories are worth stating so the omissions do not read as oversights. Each names commercial terms, a competitor, a customer, or a private individual:

One item is published with care rather than withheld: the somebody has to be the villagers argument about non-functional requirements is strong and belongs here, but its market statistics are loosely attributed — the brief itself flags that "much of what circulates is vendor commentary recycling a smaller set of underlying studies" — so the argument is used and the numbers are not.