for agents/llms.txtv0.5.6 · 22 Sep 2026

Home / About the author

The person behind the first-person articles

Dinis Cruz

sgit.ai is built by one person and a team of agents, and the articles here that say I are written by the person. This page is the provenance for that byline: who I am, what I have built, where else I write, and the interests a reader should know about before taking the argument. It follows the same rule as the rest of the site, which is that a claim should be checkable without trusting me.

The record

RoleWhat it involves
Founder, sgit.aiEncrypted vaults with git semantics: clone, commit, branch and merge files that are encrypted before they leave your machine, under Apache-2.0, and the network of sites of which this is the hub. Each site publishes its argument before its implementation, so the commitments are checkable, and thirty-one vaults are published with their read keys as the evidence.
Founder, sgraph.aiWhere the strategy turns into revenue: the commercial home of SG/Send, the secure file-sharing service built on the open-source sgit layer, and hosted SG/Vaults. The code stays Apache-2.0. What is sold is the running, maintained, certified service.
Founder, MyFeeds.aiRole-aware cybersecurity briefings built on semantic knowledge graphs, with source attribution: CISO, engineer and board views of the same news. Open source, serverless, and with the seed pitch and unit economics published in the open.
Founder, The Cyber BoardroomAn AI-powered platform for the conversation between technical security teams and the board, bridging the two with knowledge-graph technology. Apache-2.0, with the community edition and the investment repository public.
Founder, RiskMandate.aiThe business risk layer for autonomous systems. Its field demo is published here as a vault, 124 files and 98 commits inside one encrypted store.
Founder, VoiceDebrief.aiVoice recordings into transcripts and debriefs, entirely in the browser, with nothing uploaded to a server. The vault where Fractal Semantic Graphs were first worked came out of this work.
Former OWASP Board memberAnd organiser of the OWASP Summits, Lisbon 2011 and Woburn 2017, the working-session format with no spectators and only participants that the Open Security Summit series went on to build on. Current open-source work still ships under the owasp-sbot organisation.
Creator, the O2 PlatformThe OWASP static-analysis engine of 2010 to 2012, and the first of a line of open-source tooling that continues in the osbot and mgraph families, memory_fs, Issues-FS and sgit-ai, all Apache-2.0 and all on PyPI.

Writing on this site

The articles carry a byline when they are written in the first person, and the byline links here. The unsigned articles are written in the site's own voice by the team of agents, from briefs, and say so.

Writing elsewhere

docs.diniscruz.aiThe long-form research and essays, including the future-of-news series from February to July 2025 that the news article here builds on. Published under CC BY 4.0.
LinkedInWhere most of the articles are first posted and discussed, and the fastest route to reach me.
open-source.sgit.aiMy position on open source as a strategy, with a fuller version of this page: the licences, the investor materials published in the open, and the interests declared there.
wardley-maps.sgit.aiThe maps behind the strategy arguments, on the principle that maps are claims, not pictures.
graphs.sgit.aiThe Fractal Semantic Graphs argument in full: the grammar, the books, the worked examples and the evidence estate.
newsroom.sgit.aiThe newsroom design the news article draws on, and its Portuguese newsroom, where I am the named editor of record.
GitHubThe code, including the sgit CLI and this site's source, every page as content files plus the build that renders them.

Interests declared

I run companies whose strategy the articles here describe, and which sell the running, maintained service rather than the code. The market the news article, the SaaS article and the startups section describe is one I intend to be in. Read the arguments knowing that. Two things are built in to keep it honest.

Reach me, or correct me

LinkedIn is the fastest route. Corrections and requests for this site are tracked in the open on the board, and the repository takes issues and pull requests. If you find something wrong here, I would rather know.