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.
- sgit.ai, complete documentation, single file 650 chars
- sgit (the encrypted git for humans and AI agents) 442 chars
- A vault is a unit of work: 6,391 chars
- on another machine (or another agent) 121 chars
- one call: encrypt, commit, push, machine-readable result 58 chars
- no working-directory scan, no full clone needed 8,398 chars
- The vault catalogue, sgit.ai 470 chars
- The vault catalogue 3,021 chars
- Comparisons, as tests you can re-run, sgit.ai 367 chars
- Comparisons, as tests you can re-run 12,212 chars
- Published vaults, sgit.ai 389 chars
- Published vaults 9,396 chars
- Start with an AI decision, then trace it back to the guidance: the DSIT AI Risk Toolkit vault 896 chars
- Start with an AI decision, then trace it back to the guidance 15,363 chars
- Publishing a vault: the method, sgit.ai 510 chars
- Publishing a vault: the method 7,644 chars
- The same pack, written for an archetype instead of a company, fractional CISO pack 598 chars
- The same pack, written for an archetype instead of a company 7,135 chars
- An application for a job, as a vault, interim CISO pack 481 chars
- An application for a job, as a vault 9,064 chars
- Synthetic users, second run, five people who do not exist, reading riskmandate.ai 533 chars
- Synthetic users, second run, five people who do not exist, reading riskmandate.ai 8,342 chars
- Synthetic users, five people who do not exist, shopping 500 chars
- Synthetic users, five people who do not exist, shopping 11,579 chars
- The sgit.ai board, a published vault 456 chars
- The site's own board, as a vault 4,349 chars
- Field Notes, a published vault 340 chars
- Field Notes 1,985 chars
- Strategy Maps (a published vault) 359 chars
- Strategy Maps 2,028 chars
- Deploy Docs, a published vault 349 chars
- Deploy Docs 1,980 chars
- The Vault Catalogue (a published vault) 375 chars
- The Vault Catalogue 1,952 chars
- Supplement Stack, a published vault 478 chars
- Supplement Stack 8,671 chars
- Risk Mandate, a published vault 388 chars
- Risk Mandate 6,406 chars
- Agentic Browser Isolation, a published vault 466 chars
- Agentic Browser Isolation 6,388 chars
- Risk Graph Explorer, a published vault 436 chars
- Risk Graph Explorer 6,759 chars
- The seven views, explained (Risk Graph Explorer) 506 chars
- The seven views, explained 9,443 chars
- The author’s walkthroughs, Risk Graph Explorer 428 chars
- The author’s walkthroughs 27,024 chars
- Algarve · May 2026, a published vault 423 chars
- Algarve · May 2026 7,843 chars
- Demos, sgit.ai 253 chars
- Demos 4,296 chars
- Fractal Semantic Graphs, sgit.ai 679 chars
- Fractal Semantic Graphs 32,279 chars
- Performance, cost, and running everywhere, Fractal Semantic Graphs 835 chars
- Performance, cost, and running everywhere 52,130 chars
- A vault app, live inside this page, sgit.ai demos 358 chars
- A vault app, live inside this page 9,759 chars
- The Strategy in Seven Maps, a real document republished from a vault, sgit.ai demos 519 chars
- A real strategy document, republished from a vault 4,541 chars
- sgit, on a Wardley Map (sgit.ai demos) 394 chars
- sgit, on a Wardley Map 3,034 chars
- Use cases, sgit 304 chars
- Use cases 5,198 chars
- The serialised pull request, sgit use cases 486 chars
- The serialised pull request 5,696 chars
- Agent state that isn't the vendor's to read, sgit use cases 337 chars
- Agent state that isn't the vendor's to read 5,725 chars
- Working documents with clients, sgit use cases 340 chars
- Working documents with clients 4,566 chars
- Findings about your own weaknesses, sgit use cases 341 chars
- Findings about your own weaknesses 4,515 chars
- Data that changes what is permissible, sgit use cases 304 chars
- Data that changes what is permissible 7,222 chars
- Case studies, sgit.ai 296 chars
- Case studies 3,549 chars
- Lessons learned, the rules and the incidents behind them, sgit.ai 514 chars
- Lessons learned 6,652 chars
- One working tree, two version control systems, and why we stopped, sgit.ai case study 622 chars
- One working tree, two version control systems, and why we stopped 9,685 chars
- Deleting files from git history, and why they are still on GitHub afterwards, sgit.ai case study 663 chars
- Deleting files from a repository's history, and why they are still on GitHub afterwards 14,764 chars
- Security model, sgit 227 chars
- Security model 6,879 chars
- Why does this exist?, sgit.ai 273 chars
- Why does this exist? 25,611 chars
- Run your own SG/Send server (sgit.ai) 276 chars
- Run your own SG/Send server 2,147 chars
- A live site whose host cannot read it, sgit.ai case study 365 chars
- How this page works 6,566 chars
- Try sgit in your browser, sgit.ai 246 chars
- Try sgit in your browser 2,066 chars
- Skills for AI agents, sgit 223 chars
- Skills, sgit for AI agents 3,136 chars
- Documentation, sgit 175 chars
- Documentation 2,434 chars
- What is sgit, Docs 217 chars
- What is sgit 2,511 chars
- Installation, sgit Docs 225 chars
- Installation 808 chars
- Quickstart, sgit Docs 209 chars
- Quickstart 1,898 chars
- sgit for git users, Docs 221 chars
- sgit for git users 2,433 chars
- The two-branch model, sgit Docs 233 chars
- The two-branch model 2,720 chars
- Working with AI agents, sgit Docs 233 chars
- Working with AI agents 3,141 chars
- When NOT to use sgit, Docs 186 chars
- When NOT to use sgit 3,747 chars
- The day we leaked our own vault key (sgit.ai case study) 288 chars
- If a vault key is exposed 6,400 chars
- Cross-team briefs, sgit.ai 240 chars
- Cross-team briefs 26,643 chars
- How the site is run, the agentic team behind sgit.ai 401 chars
- How this site is run 7,814 chars
- Starting prompts for the regular work (sgit.ai team) 468 chars
- Starting prompts for the regular work 10,313 chars
- The board, open work on sgit.ai, as a kanban of files 395 chars
- The board 9,354 chars
- Four sheets, four audiences, one stack, the Lisbon summit handouts 400 chars
- Four sheets, four audiences, one stack 2,893 chars
- Founders, open source technology that works today 435 chars
- Founders, Open source technology that works today 3,134 chars
- Startups. It is open source, and it is built to be built on 381 chars
- Startups, Let’s build together 2,546 chars
- Investors (how does your firm share data with its portfolio?) 447 chars
- Investors, How does your firm share data with its portfolio? 2,748 chars
- Corporate users, services available now 423 chars
- Corporate users, Services available now 2,828 chars
- sgit.ai, for investors, published in the open 480 chars
- sgit.ai, for investors 9,806 chars
- Build your startup on sgit vaults, sgit.ai 598 chars
- Build your startup on sgit vaults 12,240 chars
- Business plans to build on sgit, sgit.ai 592 chars
- Business plans to build on sgit 7,208 chars
- About the author, Dinis Cruz, sgit.ai 465 chars
- Dinis Cruz 7,475 chars
- Partnerships, argued in the open, sgit.ai 492 chars
- Partnerships, argued in the open 4,051 chars
- A proposed partnership between sgit.ai, RiskMandate.ai and UK Sovereign AI 1,052 chars
- A proposed partnership between sgit.ai, RiskMandate.ai and UK Sovereign AI 19,381 chars
- Who holds the keys? A call for collaboration on vault key management, sgit.ai 995 chars
- Who holds the keys? A call for collaboration on vault key management 20,904 chars
- sgit runs on every cloud: proposed partnerships with the cloud platforms, sgit.ai 742 chars
- sgit runs on every cloud. We would like to work with them properly. 12,119 chars
- A proposed partnership between sgit.ai and AWS 745 chars
- A proposed partnership between sgit.ai and AWS 5,579 chars
- A proposed partnership between sgit.ai and Microsoft Azure 763 chars
- A proposed partnership between sgit.ai and Microsoft Azure 5,632 chars
- A proposed partnership between sgit.ai and Google Cloud 697 chars
- A proposed partnership between sgit.ai and Google Cloud 4,694 chars
- A proposed partnership between sgit.ai and IBM Cloud 729 chars
- A proposed partnership between sgit.ai and IBM Cloud 4,255 chars
- A proposed partnership between sgit.ai and the European clouds 847 chars
- A proposed partnership between sgit.ai and the European clouds 5,452 chars
- A proposed partnership between sgit.ai and DigitalOcean 688 chars
- A proposed partnership between sgit.ai and DigitalOcean 3,617 chars
- A proposed partnership between sgit.ai and Rackspace Technology 759 chars
- A proposed partnership between sgit.ai and Rackspace Technology 3,876 chars
- A proposed partnership between sgit.ai and Netlify 700 chars
- A proposed partnership between sgit.ai and Netlify 3,832 chars
- Models do the work, vaults hold it: proposed partnerships with the AI providers, sgit.ai 678 chars
- Models do the work. Vaults hold it. We would like to work with the people who make the models. 7,476 chars
- A proposed partnership between sgit.ai and OpenAI 750 chars
- A proposed partnership between sgit.ai and OpenAI 4,723 chars
- A proposed partnership between sgit.ai and Anthropic 765 chars
- A proposed partnership between sgit.ai and Anthropic 4,906 chars
- A proposed partnership between sgit.ai and Mistral AI 734 chars
- A proposed partnership between sgit.ai and Mistral AI 4,492 chars
- A proposed partnership between sgit.ai and Google Gemini 750 chars
- A proposed partnership between sgit.ai and Google Gemini 4,301 chars
- A proposed partnership between sgit.ai and OpenRouter 764 chars
- A proposed partnership between sgit.ai and OpenRouter 4,322 chars
- A proposed partnership between sgit.ai and ElevenLabs 732 chars
- A proposed partnership between sgit.ai and ElevenLabs 4,461 chars
- For RiskMandate.ai: an interview page, and a ChatGPT voice prompt to run it 684 chars
- For RiskMandate.ai: an interview page, and a ChatGPT voice prompt to run it 11,911 chars
- For RiskMandate.ai: the risk side of the partnerships, and a risk mapping for sgit 771 chars
- For RiskMandate.ai: the risk side of the partnerships, and a risk mapping for sgit 14,731 chars
- Telemetry from a published vault, a build brief 542 chars
- Telemetry from a published vault 14,948 chars
- Working on a vault: start here, guidance 488 chars
- Working on a vault: start here 9,834 chars
- Three surfaces: which one are you building for?, sgit.ai 416 chars
- Three surfaces, which one are you building for? 5,386 chars
- Reading a vault from a .sgit.ai site page, build brief 645 chars
- Reading a vault from a .sgit.ai site page 8,643 chars
- Publishing a vault’s decks onto a website, build brief 649 chars
- Publishing a vault's decks onto a website 11,044 chars
- For graphs.sgit.ai: Fractal Semantic Graphs, and what to change 738 chars
- Fractal Semantic Graphs: what graphs.sgit.ai should take from the sgit.ai page 17,706 chars
- An infographic of the published vaults, build brief 615 chars
- An infographic of the published vaults, grouped by use case and industry 10,043 chars
- Markdown and file viewers in a vault: what not to build (build brief) 619 chars
- Markdown and file viewers in a vault: what not to build 8,951 chars
- SG/Vault & the vault platform, sgit.ai 267 chars
- SG/Vault & the vault platform 3,521 chars
- Building vault apps, SG/Vault 371 chars
- Building vault apps 3,926 chars
- The window.sg bridge, SG/Vault 370 chars
- The window.sg bridge 6,330 chars
- Content authoring, SG/Vault 412 chars
- Publishing content without code 4,062 chars
- Sub-vaults, SG/Vault 278 chars
- Sub-vaults: vaults inside vaults 3,580 chars
- Git repos inside vaults, SG/Vault 324 chars
- Git repos inside vaults 8,690 chars
- Reading one file out of a vault, SG/Vault 553 chars
- Reading one file out of a vault, from any web page 8,528 chars
- Static hosting on GitHub Pages, SG/Vault 325 chars
- Static hosting, GitHub Pages / S3 3,207 chars
- Admin & engineering, sgit.ai 257 chars
- Admin & engineering 5,142 chars
- Release history, sgit.ai 243 chars
- Release history 260,121 chars
- The HTTP API, sgit.ai 357 chars
- The HTTP API 4,563 chars
- API authentication, sgit.ai 363 chars
- Authentication 2,716 chars
- API: vault objects, sgit.ai 343 chars
- Vault objects 4,397 chars
- API: append lanes (sgit.ai) 344 chars
- Append lanes 6,798 chars
- API: transfers, one encrypted handover, one link 457 chars
- The transfer API, one encrypted handover, one link 9,570 chars
- API errors and limits, sgit.ai 313 chars
- Errors and limits 2,260 chars
- Sending messages between vaults, sgit.ai 424 chars
- Sending messages between vaults 9,265 chars
- Vault credentials: what each one can do, and what its prefix declares, sgit.ai 587 chars
- Vault credentials: what each one can do, and what its prefix declares 6,061 chars
- Keys, signatures and encrypting to someone else, sgit.ai 338 chars
- Keys, signatures and encrypting to someone else 5,919 chars
- Updates (sgit.ai) 240 chars
- Updates 168,153 chars
- Articles, sgit.ai 275 chars
- Articles 9,587 chars
- The sgit.ai network, sibling sites 350 chars
- The sgit.ai network 20,238 chars
- Vault App Mode, a published vault 440 chars
- Vault App Mode, nine POCs and a demo 16,196 chars
- Private Health Score, a published vault 491 chars
- Private Health Score 14,111 chars
- VoiceDebrief, a published vault 413 chars
- VoiceDebrief · Fractal Semantic Graphs 16,908 chars
- Regulation Graph, a published vault 449 chars
- Regulation Graph 8,361 chars
- SG/Payments Brief Pack, a published vault 390 chars
- SG/Payments Brief Pack 3,270 chars
- Agent as Webmaster, a business plan published as a vault 608 chars
- Agent as Webmaster, a business plan for somebody else to run 10,136 chars
- Connector Twin, a business plan with a working replay, published as a vault 695 chars
- Connector Twin, a business plan with a working replay 9,048 chars
- Risk Acceptance Office, a business plan with one risk replayed, published as a vault 751 chars
- Risk Acceptance Office, a business plan with one risk replayed 7,179 chars
- Lesson Loop, a business plan for coaches with one player's record, published as a vault 745 chars
- Lesson Loop, a business plan for coaches with one player's record 7,514 chars
- Company X-Ray, a business plan with one company X-rayed, published as a vault 783 chars
- Company X-Ray, a business plan with one company X-rayed 10,361 chars
- SG Commercialisation, a published vault 385 chars
- SG Commercialisation 2,981 chars
- RiskMandate: File security, a published vault 419 chars
- RiskMandate, File security 3,000 chars
- Standards Atlas: GDPR, a published vault 457 chars
- Standards Atlas, GDPR 5,161 chars
- Content-Transformation Proxy, a published vault 394 chars
- Content-Transformation Proxy 2,962 chars
- Penetration Test Report, a published vault 450 chars
- Penetration Test Report 3,413 chars
- AI vs. AI, Black Hat Europe 2025, a published vault 447 chars
- AI vs. AI, Black Hat Europe 2025 5,984 chars
- Scaling Threat Modeling with Semantic Knowledge Graphs, a published vault 492 chars
- Scaling Threat Modeling with Semantic Knowledge Graphs 6,749 chars
- AIUC-1, as a graph you can cite, a published vault 530 chars
- AIUC-1, as a graph you can cite 7,196 chars
- Provenance is not conformance, a published vault 567 chars
- Provenance is not conformance 15,657 chars
- A three-minute pitch, delivered from a vault, a published vault 457 chars
- A three-minute pitch, delivered from a vault 4,555 chars
- Two games about agent permissions (a published vault) 524 chars
- Two games about what an agent can do, and the first vault here that phones home 12,215 chars
- Licence to Operate (an insurance policy for an agent, simulated) a published vault 476 chars
- Licence to Operate, an insurance policy for an agent, simulated 6,816 chars
- Seven shorts on the licence to operate, the author's walkthroughs 590 chars
- Seven shorts on the licence to operate 11,314 chars
- The AIUC-1 conformance layer decks, sgit.ai 367 chars
- The AIUC-1 conformance layer decks 1,637 chars
- What AIUC-1 is, AIUC-1 conformance layer decks 395 chars
- What AIUC-1 is 1,410 chars
- The vault: files, graphs, and the query (AIUC-1 conformance layer decks) 435 chars
- The vault: files, graphs, and the query 1,527 chars
- How RiskMandate.ai's insurance model works with AIUC-1, AIUC-1 conformance layer decks 469 chars
- How RiskMandate.ai's insurance model works with AIUC-1 1,603 chars
- Zoom in: D003 (one control, to the byte, measured, and run) AIUC-1 conformance layer decks 534 chars
- Zoom in: D003, one control, to the byte, measured, and run 1,602 chars
- The Licence to Operate decks, sgit.ai 355 chars
- The Licence to Operate decks 1,969 chars
- The problem (Licence to Operate decks) 387 chars
- The problem 1,731 chars
- The map (Licence to Operate decks) 482 chars
- The map 1,909 chars
- Bounding it, Licence to Operate decks 424 chars
- Bounding it 1,827 chars
- Who says yes, Licence to Operate decks 440 chars
- Who says yes 1,833 chars
- The insurance model, Licence to Operate decks 413 chars
- The insurance model 1,773 chars
- Before you give an agent a connector, give the connector a twin, sgit.ai 1,246 chars
- Before you give an agent a connector, give the connector a twin 21,096 chars
- Every risk is already accepted. The only question is by whom, and for how long., sgit.ai 1,529 chars
- Every risk is already accepted. The only question is by whom, and for how long. 22,415 chars
- The future of news is the story vault, not the paywall, sgit.ai 1,503 chars
- The future of news is the story vault, not the paywall 49,441 chars
- The SaaS apocalypse will be decided by inertia, not by AI, sgit.ai 1,370 chars
- The SaaS apocalypse will be decided by inertia, not by AI 22,607 chars
- For a startup, the most important question is whether they miss it, sgit.ai 618 chars
- For a startup, the most important question is whether they miss it 10,453 chars
- Fractal Semantic Graphs: everything connects to everything, and nobody has to share a schema, sgit.ai 673 chars
- Fractal Semantic Graphs: everything connects to everything, and nobody has to share a schema 16,330 chars
- The proof is two clicks behind the claim, what the homepage gets wrong, and the fix, sgit.ai 625 chars
- The proof is two clicks behind the claim, what the homepage gets wrong, and the fix 9,115 chars
- The proof moved up, the homepage after the rebuild, next to the before pictures, sgit.ai 536 chars
- The proof moved up, the homepage after the rebuild, next to the before pictures 5,633 chars
- A chat box on a site with no server, the plan, and the trade it makes, sgit.ai 555 chars
- A chat box on a site with no server, the plan, and the trade it makes 7,021 chars
- Twenty sites in fifteen days, and what that did to the writing, sgit.ai 454 chars
- Twenty sites in fifteen days, and what that did to the writing 5,651 chars
- Git for things you cannot put on GitHub, sgit.ai 402 chars
- Git for things you cannot put on GitHub 7,155 chars
- Seven vaults, one method, sgit.ai 431 chars
- Seven vaults, one method 6,969 chars
- Green does not mean live, sgit.ai 397 chars
- Green does not mean live 5,141 chars
- Sherpa, an agentic role on sgit.ai 290 chars
- Sherpa 2,895 chars
- Publisher, an agentic role on sgit.ai 383 chars
- Publisher 4,057 chars
- Auditor, an agentic role on sgit.ai 348 chars
- Auditor 3,614 chars
- Journalist, an agentic role on sgit.ai 373 chars
- Journalist 3,318 chars
- Cartographer, an agentic role on sgit.ai 384 chars
- Cartographer 3,466 chars
- Ambassador, an agentic role on sgit.ai 347 chars
- Ambassador 3,361 chars
- Designer, an agentic role on sgit.ai 362 chars
- Designer 3,596 chars
- Release engineer, an agentic role on sgit.ai 308 chars
- Release engineer 3,682 chars
- Historian, an agentic role on sgit.ai 379 chars
- Historian 2,977 chars
- graphs.sgit.ai, A node is just a node, meaning lives in the edges, sgit.ai 477 chars
- graphs.sgit.ai 9,155 chars
- nhi.sgit.ai, Agents you run, agents you rent, and the identity gap, sgit.ai 475 chars
- nhi.sgit.ai 2,880 chars
- pki.sgit.ai, A key registry for agents, designed from a documented failure, sgit.ai 459 chars
- pki.sgit.ai 3,733 chars
- sg-sentinel.sgit.ai, An app-coupled edge guard, Layer 1 decides, Layer 2 acts, sgit.ai 489 chars
- sg-sentinel.sgit.ai 5,400 chars