sgit newsroom v0.1.29 · snapshot 2026-09-24

Reading room · sgit.ai

Reading room / sgit.ai · raw text · live ↗

sgit.ai: everything, in 358 sections

The site's llms-full.txt (1,877,074 bytes) is split here on its headings so it reads as pages, not one scroll. The frozen file is unchanged: raw text.

  1. sgit.ai, complete documentation, single file 650 chars
  2. sgit (the encrypted git for humans and AI agents) 442 chars
  3. A vault is a unit of work: 6,391 chars
  4. on another machine (or another agent) 121 chars
  5. one call: encrypt, commit, push, machine-readable result 58 chars
  6. no working-directory scan, no full clone needed 8,398 chars
  7. The vault catalogue, sgit.ai 470 chars
  8. The vault catalogue 3,021 chars
  9. Comparisons, as tests you can re-run, sgit.ai 367 chars
  10. Comparisons, as tests you can re-run 12,212 chars
  11. Published vaults, sgit.ai 389 chars
  12. Published vaults 9,396 chars
  13. Start with an AI decision, then trace it back to the guidance: the DSIT AI Risk Toolkit vault 896 chars
  14. Start with an AI decision, then trace it back to the guidance 15,363 chars
  15. Publishing a vault: the method, sgit.ai 510 chars
  16. Publishing a vault: the method 7,644 chars
  17. The same pack, written for an archetype instead of a company, fractional CISO pack 598 chars
  18. The same pack, written for an archetype instead of a company 7,135 chars
  19. An application for a job, as a vault, interim CISO pack 481 chars
  20. An application for a job, as a vault 9,064 chars
  21. Synthetic users, second run, five people who do not exist, reading riskmandate.ai 533 chars
  22. Synthetic users, second run, five people who do not exist, reading riskmandate.ai 8,342 chars
  23. Synthetic users, five people who do not exist, shopping 500 chars
  24. Synthetic users, five people who do not exist, shopping 11,579 chars
  25. The sgit.ai board, a published vault 456 chars
  26. The site's own board, as a vault 4,349 chars
  27. Field Notes, a published vault 340 chars
  28. Field Notes 1,985 chars
  29. Strategy Maps (a published vault) 359 chars
  30. Strategy Maps 2,028 chars
  31. Deploy Docs, a published vault 349 chars
  32. Deploy Docs 1,980 chars
  33. The Vault Catalogue (a published vault) 375 chars
  34. The Vault Catalogue 1,952 chars
  35. Supplement Stack, a published vault 478 chars
  36. Supplement Stack 8,671 chars
  37. Risk Mandate, a published vault 388 chars
  38. Risk Mandate 6,406 chars
  39. Agentic Browser Isolation, a published vault 466 chars
  40. Agentic Browser Isolation 6,388 chars
  41. Risk Graph Explorer, a published vault 436 chars
  42. Risk Graph Explorer 6,759 chars
  43. The seven views, explained (Risk Graph Explorer) 506 chars
  44. The seven views, explained 9,443 chars
  45. The author’s walkthroughs, Risk Graph Explorer 428 chars
  46. The author’s walkthroughs 27,024 chars
  47. Algarve · May 2026, a published vault 423 chars
  48. Algarve · May 2026 7,843 chars
  49. Demos, sgit.ai 253 chars
  50. Demos 4,296 chars
  51. Fractal Semantic Graphs, sgit.ai 679 chars
  52. Fractal Semantic Graphs 32,279 chars
  53. Performance, cost, and running everywhere, Fractal Semantic Graphs 835 chars
  54. Performance, cost, and running everywhere 52,130 chars
  55. A vault app, live inside this page, sgit.ai demos 358 chars
  56. A vault app, live inside this page 9,759 chars
  57. The Strategy in Seven Maps, a real document republished from a vault, sgit.ai demos 519 chars
  58. A real strategy document, republished from a vault 4,541 chars
  59. sgit, on a Wardley Map (sgit.ai demos) 394 chars
  60. sgit, on a Wardley Map 3,034 chars
  61. Use cases, sgit 304 chars
  62. Use cases 5,198 chars
  63. The serialised pull request, sgit use cases 486 chars
  64. The serialised pull request 5,696 chars
  65. Agent state that isn't the vendor's to read, sgit use cases 337 chars
  66. Agent state that isn't the vendor's to read 5,725 chars
  67. Working documents with clients, sgit use cases 340 chars
  68. Working documents with clients 4,566 chars
  69. Findings about your own weaknesses, sgit use cases 341 chars
  70. Findings about your own weaknesses 4,515 chars
  71. Data that changes what is permissible, sgit use cases 304 chars
  72. Data that changes what is permissible 7,222 chars
  73. Case studies, sgit.ai 296 chars
  74. Case studies 3,549 chars
  75. Lessons learned, the rules and the incidents behind them, sgit.ai 514 chars
  76. Lessons learned 6,652 chars
  77. One working tree, two version control systems, and why we stopped, sgit.ai case study 622 chars
  78. One working tree, two version control systems, and why we stopped 9,685 chars
  79. Deleting files from git history, and why they are still on GitHub afterwards, sgit.ai case study 663 chars
  80. Deleting files from a repository's history, and why they are still on GitHub afterwards 14,764 chars
  81. Security model, sgit 227 chars
  82. Security model 6,879 chars
  83. Why does this exist?, sgit.ai 273 chars
  84. Why does this exist? 25,611 chars
  85. Run your own SG/Send server (sgit.ai) 276 chars
  86. Run your own SG/Send server 2,147 chars
  87. A live site whose host cannot read it, sgit.ai case study 365 chars
  88. How this page works 6,566 chars
  89. Try sgit in your browser, sgit.ai 246 chars
  90. Try sgit in your browser 2,066 chars
  91. Skills for AI agents, sgit 223 chars
  92. Skills, sgit for AI agents 3,136 chars
  93. Documentation, sgit 175 chars
  94. Documentation 2,434 chars
  95. What is sgit, Docs 217 chars
  96. What is sgit 2,511 chars
  97. Installation, sgit Docs 225 chars
  98. Installation 808 chars
  99. Quickstart, sgit Docs 209 chars
  100. Quickstart 1,898 chars
  101. sgit for git users, Docs 221 chars
  102. sgit for git users 2,433 chars
  103. The two-branch model, sgit Docs 233 chars
  104. The two-branch model 2,720 chars
  105. Working with AI agents, sgit Docs 233 chars
  106. Working with AI agents 3,141 chars
  107. When NOT to use sgit, Docs 186 chars
  108. When NOT to use sgit 3,747 chars
  109. The day we leaked our own vault key (sgit.ai case study) 288 chars
  110. If a vault key is exposed 6,400 chars
  111. Cross-team briefs, sgit.ai 240 chars
  112. Cross-team briefs 26,643 chars
  113. How the site is run, the agentic team behind sgit.ai 401 chars
  114. How this site is run 7,814 chars
  115. Starting prompts for the regular work (sgit.ai team) 468 chars
  116. Starting prompts for the regular work 10,313 chars
  117. The board, open work on sgit.ai, as a kanban of files 395 chars
  118. The board 9,354 chars
  119. Four sheets, four audiences, one stack, the Lisbon summit handouts 400 chars
  120. Four sheets, four audiences, one stack 2,893 chars
  121. Founders, open source technology that works today 435 chars
  122. Founders, Open source technology that works today 3,134 chars
  123. Startups. It is open source, and it is built to be built on 381 chars
  124. Startups, Let’s build together 2,546 chars
  125. Investors (how does your firm share data with its portfolio?) 447 chars
  126. Investors, How does your firm share data with its portfolio? 2,748 chars
  127. Corporate users, services available now 423 chars
  128. Corporate users, Services available now 2,828 chars
  129. sgit.ai, for investors, published in the open 480 chars
  130. sgit.ai, for investors 9,806 chars
  131. Build your startup on sgit vaults, sgit.ai 598 chars
  132. Build your startup on sgit vaults 12,240 chars
  133. Business plans to build on sgit, sgit.ai 592 chars
  134. Business plans to build on sgit 7,208 chars
  135. About the author, Dinis Cruz, sgit.ai 465 chars
  136. Dinis Cruz 7,475 chars
  137. Partnerships, argued in the open, sgit.ai 492 chars
  138. Partnerships, argued in the open 4,051 chars
  139. A proposed partnership between sgit.ai, RiskMandate.ai and UK Sovereign AI 1,052 chars
  140. A proposed partnership between sgit.ai, RiskMandate.ai and UK Sovereign AI 19,381 chars
  141. Who holds the keys? A call for collaboration on vault key management, sgit.ai 995 chars
  142. Who holds the keys? A call for collaboration on vault key management 20,904 chars
  143. sgit runs on every cloud: proposed partnerships with the cloud platforms, sgit.ai 742 chars
  144. sgit runs on every cloud. We would like to work with them properly. 12,119 chars
  145. A proposed partnership between sgit.ai and AWS 745 chars
  146. A proposed partnership between sgit.ai and AWS 5,579 chars
  147. A proposed partnership between sgit.ai and Microsoft Azure 763 chars
  148. A proposed partnership between sgit.ai and Microsoft Azure 5,632 chars
  149. A proposed partnership between sgit.ai and Google Cloud 697 chars
  150. A proposed partnership between sgit.ai and Google Cloud 4,694 chars
  151. A proposed partnership between sgit.ai and IBM Cloud 729 chars
  152. A proposed partnership between sgit.ai and IBM Cloud 4,255 chars
  153. A proposed partnership between sgit.ai and the European clouds 847 chars
  154. A proposed partnership between sgit.ai and the European clouds 5,452 chars
  155. A proposed partnership between sgit.ai and DigitalOcean 688 chars
  156. A proposed partnership between sgit.ai and DigitalOcean 3,617 chars
  157. A proposed partnership between sgit.ai and Rackspace Technology 759 chars
  158. A proposed partnership between sgit.ai and Rackspace Technology 3,876 chars
  159. A proposed partnership between sgit.ai and Netlify 700 chars
  160. A proposed partnership between sgit.ai and Netlify 3,832 chars
  161. Models do the work, vaults hold it: proposed partnerships with the AI providers, sgit.ai 678 chars
  162. Models do the work. Vaults hold it. We would like to work with the people who make the models. 7,476 chars
  163. A proposed partnership between sgit.ai and OpenAI 750 chars
  164. A proposed partnership between sgit.ai and OpenAI 4,723 chars
  165. A proposed partnership between sgit.ai and Anthropic 765 chars
  166. A proposed partnership between sgit.ai and Anthropic 4,906 chars
  167. A proposed partnership between sgit.ai and Mistral AI 734 chars
  168. A proposed partnership between sgit.ai and Mistral AI 4,492 chars
  169. A proposed partnership between sgit.ai and Google Gemini 750 chars
  170. A proposed partnership between sgit.ai and Google Gemini 4,301 chars
  171. A proposed partnership between sgit.ai and OpenRouter 764 chars
  172. A proposed partnership between sgit.ai and OpenRouter 4,322 chars
  173. A proposed partnership between sgit.ai and ElevenLabs 732 chars
  174. A proposed partnership between sgit.ai and ElevenLabs 4,461 chars
  175. For RiskMandate.ai: an interview page, and a ChatGPT voice prompt to run it 684 chars
  176. For RiskMandate.ai: an interview page, and a ChatGPT voice prompt to run it 11,911 chars
  177. For RiskMandate.ai: the risk side of the partnerships, and a risk mapping for sgit 771 chars
  178. For RiskMandate.ai: the risk side of the partnerships, and a risk mapping for sgit 14,731 chars
  179. Telemetry from a published vault, a build brief 542 chars
  180. Telemetry from a published vault 14,948 chars
  181. Working on a vault: start here, guidance 488 chars
  182. Working on a vault: start here 9,834 chars
  183. Three surfaces: which one are you building for?, sgit.ai 416 chars
  184. Three surfaces, which one are you building for? 5,386 chars
  185. Reading a vault from a .sgit.ai site page, build brief 645 chars
  186. Reading a vault from a .sgit.ai site page 8,643 chars
  187. Publishing a vault’s decks onto a website, build brief 649 chars
  188. Publishing a vault's decks onto a website 11,044 chars
  189. For graphs.sgit.ai: Fractal Semantic Graphs, and what to change 738 chars
  190. Fractal Semantic Graphs: what graphs.sgit.ai should take from the sgit.ai page 17,706 chars
  191. An infographic of the published vaults, build brief 615 chars
  192. An infographic of the published vaults, grouped by use case and industry 10,043 chars
  193. Markdown and file viewers in a vault: what not to build (build brief) 619 chars
  194. Markdown and file viewers in a vault: what not to build 8,951 chars
  195. SG/Vault & the vault platform, sgit.ai 267 chars
  196. SG/Vault & the vault platform 3,521 chars
  197. Building vault apps, SG/Vault 371 chars
  198. Building vault apps 3,926 chars
  199. The window.sg bridge, SG/Vault 370 chars
  200. The window.sg bridge 6,330 chars
  201. Content authoring, SG/Vault 412 chars
  202. Publishing content without code 4,062 chars
  203. Sub-vaults, SG/Vault 278 chars
  204. Sub-vaults: vaults inside vaults 3,580 chars
  205. Git repos inside vaults, SG/Vault 324 chars
  206. Git repos inside vaults 8,690 chars
  207. Reading one file out of a vault, SG/Vault 553 chars
  208. Reading one file out of a vault, from any web page 8,528 chars
  209. Static hosting on GitHub Pages, SG/Vault 325 chars
  210. Static hosting, GitHub Pages / S3 3,207 chars
  211. Admin & engineering, sgit.ai 257 chars
  212. Admin & engineering 5,142 chars
  213. Release history, sgit.ai 243 chars
  214. Release history 260,121 chars
  215. The HTTP API, sgit.ai 357 chars
  216. The HTTP API 4,563 chars
  217. API authentication, sgit.ai 363 chars
  218. Authentication 2,716 chars
  219. API: vault objects, sgit.ai 343 chars
  220. Vault objects 4,397 chars
  221. API: append lanes (sgit.ai) 344 chars
  222. Append lanes 6,798 chars
  223. API: transfers, one encrypted handover, one link 457 chars
  224. The transfer API, one encrypted handover, one link 9,570 chars
  225. API errors and limits, sgit.ai 313 chars
  226. Errors and limits 2,260 chars
  227. Sending messages between vaults, sgit.ai 424 chars
  228. Sending messages between vaults 9,265 chars
  229. Vault credentials: what each one can do, and what its prefix declares, sgit.ai 587 chars
  230. Vault credentials: what each one can do, and what its prefix declares 6,061 chars
  231. Keys, signatures and encrypting to someone else, sgit.ai 338 chars
  232. Keys, signatures and encrypting to someone else 5,919 chars
  233. Updates (sgit.ai) 240 chars
  234. Updates 168,153 chars
  235. Articles, sgit.ai 275 chars
  236. Articles 9,587 chars
  237. The sgit.ai network, sibling sites 350 chars
  238. The sgit.ai network 20,238 chars
  239. Vault App Mode, a published vault 440 chars
  240. Vault App Mode, nine POCs and a demo 16,196 chars
  241. Private Health Score, a published vault 491 chars
  242. Private Health Score 14,111 chars
  243. VoiceDebrief, a published vault 413 chars
  244. VoiceDebrief · Fractal Semantic Graphs 16,908 chars
  245. Regulation Graph, a published vault 449 chars
  246. Regulation Graph 8,361 chars
  247. SG/Payments Brief Pack, a published vault 390 chars
  248. SG/Payments Brief Pack 3,270 chars
  249. Agent as Webmaster, a business plan published as a vault 608 chars
  250. Agent as Webmaster, a business plan for somebody else to run 10,136 chars
  251. Connector Twin, a business plan with a working replay, published as a vault 695 chars
  252. Connector Twin, a business plan with a working replay 9,048 chars
  253. Risk Acceptance Office, a business plan with one risk replayed, published as a vault 751 chars
  254. Risk Acceptance Office, a business plan with one risk replayed 7,179 chars
  255. Lesson Loop, a business plan for coaches with one player's record, published as a vault 745 chars
  256. Lesson Loop, a business plan for coaches with one player's record 7,514 chars
  257. Company X-Ray, a business plan with one company X-rayed, published as a vault 783 chars
  258. Company X-Ray, a business plan with one company X-rayed 10,361 chars
  259. SG Commercialisation, a published vault 385 chars
  260. SG Commercialisation 2,981 chars
  261. RiskMandate: File security, a published vault 419 chars
  262. RiskMandate, File security 3,000 chars
  263. Standards Atlas: GDPR, a published vault 457 chars
  264. Standards Atlas, GDPR 5,161 chars
  265. Content-Transformation Proxy, a published vault 394 chars
  266. Content-Transformation Proxy 2,962 chars
  267. Penetration Test Report, a published vault 450 chars
  268. Penetration Test Report 3,413 chars
  269. AI vs. AI, Black Hat Europe 2025, a published vault 447 chars
  270. AI vs. AI, Black Hat Europe 2025 5,984 chars
  271. Scaling Threat Modeling with Semantic Knowledge Graphs, a published vault 492 chars
  272. Scaling Threat Modeling with Semantic Knowledge Graphs 6,749 chars
  273. AIUC-1, as a graph you can cite, a published vault 530 chars
  274. AIUC-1, as a graph you can cite 7,196 chars
  275. Provenance is not conformance, a published vault 567 chars
  276. Provenance is not conformance 15,657 chars
  277. A three-minute pitch, delivered from a vault, a published vault 457 chars
  278. A three-minute pitch, delivered from a vault 4,555 chars
  279. Two games about agent permissions (a published vault) 524 chars
  280. Two games about what an agent can do, and the first vault here that phones home 12,215 chars
  281. Licence to Operate (an insurance policy for an agent, simulated) a published vault 476 chars
  282. Licence to Operate, an insurance policy for an agent, simulated 6,816 chars
  283. Seven shorts on the licence to operate, the author's walkthroughs 590 chars
  284. Seven shorts on the licence to operate 11,314 chars
  285. The AIUC-1 conformance layer decks, sgit.ai 367 chars
  286. The AIUC-1 conformance layer decks 1,637 chars
  287. What AIUC-1 is, AIUC-1 conformance layer decks 395 chars
  288. What AIUC-1 is 1,410 chars
  289. The vault: files, graphs, and the query (AIUC-1 conformance layer decks) 435 chars
  290. The vault: files, graphs, and the query 1,527 chars
  291. How RiskMandate.ai's insurance model works with AIUC-1, AIUC-1 conformance layer decks 469 chars
  292. How RiskMandate.ai's insurance model works with AIUC-1 1,603 chars
  293. Zoom in: D003 (one control, to the byte, measured, and run) AIUC-1 conformance layer decks 534 chars
  294. Zoom in: D003, one control, to the byte, measured, and run 1,602 chars
  295. The Licence to Operate decks, sgit.ai 355 chars
  296. The Licence to Operate decks 1,969 chars
  297. The problem (Licence to Operate decks) 387 chars
  298. The problem 1,731 chars
  299. The map (Licence to Operate decks) 482 chars
  300. The map 1,909 chars
  301. Bounding it, Licence to Operate decks 424 chars
  302. Bounding it 1,827 chars
  303. Who says yes, Licence to Operate decks 440 chars
  304. Who says yes 1,833 chars
  305. The insurance model, Licence to Operate decks 413 chars
  306. The insurance model 1,773 chars
  307. Before you give an agent a connector, give the connector a twin, sgit.ai 1,246 chars
  308. Before you give an agent a connector, give the connector a twin 21,096 chars
  309. Every risk is already accepted. The only question is by whom, and for how long., sgit.ai 1,529 chars
  310. Every risk is already accepted. The only question is by whom, and for how long. 22,415 chars
  311. The future of news is the story vault, not the paywall, sgit.ai 1,503 chars
  312. The future of news is the story vault, not the paywall 49,441 chars
  313. The SaaS apocalypse will be decided by inertia, not by AI, sgit.ai 1,370 chars
  314. The SaaS apocalypse will be decided by inertia, not by AI 22,607 chars
  315. For a startup, the most important question is whether they miss it, sgit.ai 618 chars
  316. For a startup, the most important question is whether they miss it 10,453 chars
  317. Fractal Semantic Graphs: everything connects to everything, and nobody has to share a schema, sgit.ai 673 chars
  318. Fractal Semantic Graphs: everything connects to everything, and nobody has to share a schema 16,330 chars
  319. The proof is two clicks behind the claim, what the homepage gets wrong, and the fix, sgit.ai 625 chars
  320. The proof is two clicks behind the claim, what the homepage gets wrong, and the fix 9,115 chars
  321. The proof moved up, the homepage after the rebuild, next to the before pictures, sgit.ai 536 chars
  322. The proof moved up, the homepage after the rebuild, next to the before pictures 5,633 chars
  323. A chat box on a site with no server, the plan, and the trade it makes, sgit.ai 555 chars
  324. A chat box on a site with no server, the plan, and the trade it makes 7,021 chars
  325. Twenty sites in fifteen days, and what that did to the writing, sgit.ai 454 chars
  326. Twenty sites in fifteen days, and what that did to the writing 5,651 chars
  327. Git for things you cannot put on GitHub, sgit.ai 402 chars
  328. Git for things you cannot put on GitHub 7,155 chars
  329. Seven vaults, one method, sgit.ai 431 chars
  330. Seven vaults, one method 6,969 chars
  331. Green does not mean live, sgit.ai 397 chars
  332. Green does not mean live 5,141 chars
  333. Sherpa, an agentic role on sgit.ai 290 chars
  334. Sherpa 2,895 chars
  335. Publisher, an agentic role on sgit.ai 383 chars
  336. Publisher 4,057 chars
  337. Auditor, an agentic role on sgit.ai 348 chars
  338. Auditor 3,614 chars
  339. Journalist, an agentic role on sgit.ai 373 chars
  340. Journalist 3,318 chars
  341. Cartographer, an agentic role on sgit.ai 384 chars
  342. Cartographer 3,466 chars
  343. Ambassador, an agentic role on sgit.ai 347 chars
  344. Ambassador 3,361 chars
  345. Designer, an agentic role on sgit.ai 362 chars
  346. Designer 3,596 chars
  347. Release engineer, an agentic role on sgit.ai 308 chars
  348. Release engineer 3,682 chars
  349. Historian, an agentic role on sgit.ai 379 chars
  350. Historian 2,977 chars
  351. graphs.sgit.ai, A node is just a node, meaning lives in the edges, sgit.ai 477 chars
  352. graphs.sgit.ai 9,155 chars
  353. nhi.sgit.ai, Agents you run, agents you rent, and the identity gap, sgit.ai 475 chars
  354. nhi.sgit.ai 2,880 chars
  355. pki.sgit.ai, A key registry for agents, designed from a documented failure, sgit.ai 459 chars
  356. pki.sgit.ai 3,733 chars
  357. sg-sentinel.sgit.ai, An app-coupled edge guard, Layer 1 decides, Layer 2 acts, sgit.ai 489 chars
  358. sg-sentinel.sgit.ai 5,400 chars