sgit, on a Wardley Map (sgit.ai demos)
Six Wardley Maps analysing sgit's positioning) starting with where git wins, drawn as inline SVG and served as a second app from the same encrypted vault as the SG/Send strategy essay: one vault, two entry points, one published read key.
Source: https://sgit.ai/demos/sgit-maps.html↗ · site v0.6.8 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a .md twin; internal links below point at them.
Home↗ / Demos↗ / sgit on a Wardley map
sgit, on a Wardley Map
Six maps analysing sgit's own positioning, starting with where git wins, because a map that flatters its author is not a map. It lives as a second app inside the same vault as the SG/Send strategy essay: one encrypted store, two entry points, both openable with the one read key already published on this site.
What is new here technically: a vault is not limited to one app. This vault (ookq4mn4) now carries two, index.html (the strategy essay) and sgit-maps.html (this analysis), and the embed below opens the second by passing an entry to the same host that opens the first. The maps are not images: each is drawn as inline SVG from data in the page, decrypted in your browser.
The live embed
The links between the two apps work inside the embed: the header of this analysis links to the strategy essay and back, and the embed host remounts the frame on the new entry, vault apps cross-linking under a read key.
Same vault and read key as the strategy essay demo↗, only the entry differs.
The six maps, in one paragraph each
- Version control, today: git at full strength: a commodity whose moat is the platform layer above it, all of it resting on the host reading plaintext.
- The files that cannot follow: the same need with one changed constraint, and a hole in the map where its foundation should be: nothing on the right is both versioned and unable to read you.
- sgit's move: no new verbs; invert the bottom layer instead. Encrypted, content-addressed objects make the store a commodity because it cannot read, and produce one novel component: the publishable read key.
- The boundary, on one map: both chains under one team: code flows right through git; protected files flow through sgit. The split is the layer above the protocol and the substrate below it, never the operations. One folder can run both, this site does.
- The new user: agents: durable memory, plus the serialised diff versus the write-scoped token; the evolve arrows all point away from ambient authority.
- The strategy: commoditise private version control; the value accrues to the layer above, and every component on that layer is already running on sgit.ai, including the page in the embed.
| Shape | Evidence status | Copy or reference |
|---|---|---|
| Structured analysis (positioning) | LIVE: authored for sgit.ai from the boundary-map work↗; the maps state where git wins first | Reference: the embed reads vault ookq4mn4 live; pushing a better map updates this page with no rebuild |
Related
- The Strategy in Seven Maps↗, the SG/Send half, first app in the same vault
- The boundary map in prose↗, the same argument, as the Why page
- How the embed works↗, the full walkthrough of the mechanism
← The strategy essay↗All demos →↗