wardley-maps.sgit.ai / The network
The network
This site is one of several under sgit.ai. The boundaries matter, because the fastest way to make a network of sites useless is to have three of them half-cover the same subject. What follows is who owns what, and where this site defers.
Who owns what
| Site | Owns | This site defers on |
|---|---|---|
| wardley-maps.sgit.ai | Mapping technique, doctrine, the PST pattern, the resource index, the published mapping history | — |
| graphs.sgit.ai | Graph theory, meaning through connectivity, and maps-as-graphs rendering methodology | Cross-link, do not duplicate. Its /v1/maps/ page is the methodology-and-inventory surface; this site is the technique surface. The argument lives here; the rendering methodology lives there. |
| pki.sgit.ai | PKI, agent identity, the registry MVP | Keeps the pack context. The doctrine assessment moved here, with the evidence links pointing back at it, and both of its map pages should follow. The assessment → |
| sgit.ai | The vault product, the CLI, the demos | Hosts the Strategy Maps vault (8 PNGs, client-side decrypted) and two live demo pages. Those stay where they are — the strategy-maps demo is a live demonstration of the vault decryption mechanism, and moving it would break the demo rather than relocate it. |
| risks.sgit.ai | Risk concepts, acceptance, the grounding ladder | Risk-as-an-evolution-axis is a shared idea — and an unresolved one. One link each way. |
| nhi.sgit.ai, sg-sentinel.sgit.ai | Non-human identity; the sentinel | Should link here. Currently mention Wardley zero times. |
| riskmandate.ai | Commercial | References, is not referenced. |
Four siblings mention Wardley zero times
Which is worth saying rather than quietly linking around, because in at least one case it is a hole with a specific shape.
- nhi.sgit.ai — the strongest candidate.
graphs.sgit.airecords four unrendered permissions maps from that work, including one called "Hope Driven Development" — andnhi.sgit.ai/hope/contains no maps at all. Its five-step framework is Enumerate, Map, Bound, Observe, Issue no credential. It is asking for one. Find them, render them, ship them: T5. - sg-sentinel.sgit.ai — zero mentions across 23 documents. Allowlist-versus-denylist is a natural map, and the evolution axis is the right tool for arguing about which one a control should be.
- riskmandate.ai — zero mentions. RAMM maturity is adjacent to doctrine, and the evolution-versus-maturity rule is directly about the difference between them.
- sgit.ai — has the maps and the vault, and its network page lists four sites and no mapping site. It needs a fifth entry, which is N3.
What moved, what is referenced
| Asset | Verdict |
|---|---|
| pki.sgit.ai's doctrine assessment and its JSON | Moved — here, with a stub to leave behind. Evidence links point back. |
| pki.sgit.ai's two Wardley map pages (10 maps) | Should move — T4, not yet done. |
| sgit.ai/demos/strategy-maps.html (8 PNGs, vault-served) | Referenced. It is a live demo of the vault decryption mechanism; moving it breaks the demo. |
| sgit.ai/demos/sgit-maps.html (6 inline SVGs) | Referenced. |
| graphs.sgit.ai/v1/maps/ | Referenced both ways. Its unrendered backlog is ready-made launch content for this site, and its methodology is the other half of maps-as-graphs. |
| The Strategy Maps vault (33 files, 830 KB) | Referenced. The read key is published deliberately; there is no doctrine content in it. |
Vault key discipline, since this page links to vaults. Every key on the
sgit.ai catalogue is an
sgit_rk1_ read key, published on purpose. No write
keys are exposed anywhere. Before linking any vault, confirm its write key is escrowed —
publishing a read key for a vault whose write key is lost freezes it permanently.
The release gate refuses to publish anything shaped
like a vault key at all.