The sgit.ai network

Nineteen focused sites on *.sgit.ai, each taking one question further than a section here could. They share this site's design and its discipline (sourced claims, a stated status, honest edges) and they publish their arguments before the things they describe exist, so the commitments stay checkable afterwards.

27 live, 0 with the repository and subdomain in place but nothing published yet. Screenshots are of the real sites, captured on the date each entry gives.

Which of these is mine?instant match · no key, no network

Describe what you are trying to do and I will point at the site that takes it seriously. This runs in your browser against the catalogue on this page, no key needed, nothing sent anywhere.

Optional. Answers get more conversational; the matching does not get more correct.

Bring your own key (OpenRouter). It is stored in this browser only and sent only to openrouter.ai, never to sgit.ai, which is a static site with no server to send it to. This page cannot protect it the way a vault app can: with no host there is no permission floor, so the key lives in this page's origin. llms.sgit.ai ↗↗ explains the difference, and the plan↗ explains how we intend to remove the trade-off.

Start from what you need

Each line is a question somebody actually arrives with, and the site that takes it seriously.

I need to give an AI agent an identitynhi.sgit.ai · agents you run vs agents you rent, and why only one is answered ↗ My app has to call an LLM and I do not want it holding an API keyllms.sgit.ai ↗ · the bridge that lets it call one without a credential↗ I have to sign off a risk and I do not want to rubber-stamp itrisks.sgit.ai ↗ · there is no deny button, only how long you accept it↗ I need to cite a regulation precisely, not paraphrase itstandards.sgit.ai ↗ · point at the provision, or you are asserting↗ I want to distribute public keys without a central authoritypki.sgit.ai · a key registry for agents, designed from a directory that was destroyed ↗ I am drawing a graph and want to get the edges rightgraphs.sgit.ai · five rules, and why relates-to is banned ↗ I want an issue tracker with no databaseissues-fs.sgit.ai ↗ · the issues are files and the files are a graph↗ I need somewhere disposable to run an agentsg-compute.sgit.ai ↗ · ephemeral AWS environments, one command away↗ I am deciding how to license and sustain an open-source projectopen-source.sgit.ai ↗ · open source is a strategy, not a charity↗ I keep being asked what a digital twin actually istwins.sgit.ai ↗ · an interface to reality, not a simulation of it↗ I want to protect an app at the edge without renting a WAFsg-sentinel.sgit.ai · an app-coupled edge guard, published as a design, not built ↗ I want to map a strategy without drawing a pretty picturewardley-maps.sgit.ai ↗ · maps are claims, not pictures↗ I need the requirements nobody writes down until they breaknfrs.sgit.ai ↗ · resilience, budgets and backups, from the inside↗ I want to know how this code is actually writtencoding.sgit.ai ↗ · the style guide that measured itself↗ I am pricing something and rent feels wrongsubscriptions.sgit.ai ↗ · a subscription is a discount for regular use, not rent↗ I care where a published fact came fromnewsroom.sgit.ai ↗ · the story is a graph; the article is a projection↗ I just want the pictureinfographics.sgit.ai ↗ · every rendered brief in one catalogue↗

Agents & AI

chrome-extensions.sgit.aiThe expensive bugs do not throw.Guidance and worked examples for building Chrome extensions, written for the agent that reads them before writing one, from five weeks building a Manifest V3 recorder against a changing, undocumented target: the method, the architecture and the failure modes.↗ v0.1.0Open chrome-extensions.sgit.ai ↗↗

coding.sgit.aiThe style guide that measured itself.How software actually gets written across this family: the rules, the compliance measurement against them, which rules are machine-enforced and which are explicitly not, and the open tensions. Includes a section on writing code for agents to read.↗ v0.2.0Open coding.sgit.ai ↗↗

elevenlabs.providers.sgit.aiWhat it cost on a named workload, on a named date.An independent report on the ElevenLabs API: what it cost on a named workload on a named date, what broke, and which of four client-side credential patterns the product can actually support.↗ v0.3.0Open elevenlabs.providers.sgit.ai ↗↗

games.sgit.aiA game makes you say what you think, before you are told.Why this family builds games: a game is the only artefact that makes somebody state a belief before they are told the answer. The catalogue, the method, and how to build one as a vault.↗ v0.4.1Open games.sgit.ai ↗↗

llms.sgit.aiYour app calls a language model without ever holding an API key.The sg.llm.* bridge: how an app running inside a vault reaches a model with no credential of its own. The reference, the traps, a four-layer security ladder, the attached-file question, and a pre-ship checklist.↗ reference draftv0.2.0Open llms.sgit.ai ↗↗

nhi.sgit.aiThe question splits into two populations, and the industry only answers oneThe question of how to give an AI agent an identity splits into two populations, and every product on the market answers only the first. For the agents you actually name (the ones running in Claude, Codex or behind an API) the honest current answer is to hand over a broad credential and hope. ↗ v0.1.14What it argues → ↗ · Open nhi.sgit.ai ↗↗

providers.sgit.aiWhere the key goes.The hub of the *.providers.sgit.ai family: four credential patterns, one page contract, and one site per provider reporting what it cost on a named workload, what broke, and where the key has to live.↗ v0.1.1Open providers.sgit.ai ↗↗

skills.sgit.aiSkills are software packages, and here is the proof.Eight skills shipped, generated from their own frontmatter; 25 briefs and 60,782 words of theory a long way ahead of them; and the diverging duplicate that is the thesis failing, live, on the estate's own skills.↗ v0.1.0Open skills.sgit.ai ↗↗

teams.sgit.aiRoles are boundaries. The Conductor never does the work.The reference for setting up agentic teams with more than one role, measured from 39 ROLE.md files across four team instantiations.↗ v0.1.0Open teams.sgit.ai ↗↗

ungovr.providers.sgit.aiOne derivable hop away.An independent report on the UnGovr Open Data API: 327,138 government entities, 398 open-records laws, free under CC BY 4.0, and a join between them that is one derivable hop away.↗ v0.1.14Open ungovr.providers.sgit.ai ↗↗

what-can-it-do.games.sgit.aiYou score for how well you know what you know.A five-minute game: name the AI assistant you use, answer forty questions about what it can do and whether you wanted it to, and score for how well you know what you know. Free, no sign-up.↗ v0.6.0Open what-can-it-do.games.sgit.ai ↗↗

Risk & governance

nfrs.sgit.aiThe non-functional requirements, from the inside.The requirements nobody writes down until they are violated (resilience, budgets, project management, backups) treated as a reality system rather than a checklist. Includes an honest column: a scorecard, and a page naming backups as a gap.↗ v0.1.2Open nfrs.sgit.ai ↗↗

risks.sgit.aiYou cannot deny a risk. You can only say how long you accept it.Risk management inverted: a named human underwrites an exposure that already exists, insurance-style, with personal liability attached. There is no deny button, the only choice is how long, and the interval is the decision. 42 concepts, a six-rung interval ladder, and a stated zero lines of code implementing any of it.↗ research sitev0.1.0Open risks.sgit.ai ↗↗

standards.sgit.aiPoint at the provision, or you are asserting.Laws, standards and frameworks as addressable graphs rather than PDFs to paraphrase. A citation scheme, a grounding ladder, and worked instruments (the EU AI Act, GDPR, ISO/IEC 27001, ISO 31000) with a subset method for handing an agent only the part that applies.↗ v0.1.4Open standards.sgit.ai ↗↗

threat-modeling.sgit.aiA threat model is a claim you can check.A threat model is a claim about a system, and this site's job is to show claims being checked: the ThreatModCon 2025 vault, a threat model validated against the code, seven white papers, and the redacted method behind them.↗ Open threat-modeling.sgit.ai ↗↗

Graphs & method

graphs.sgit.aiA node is just a node. Meaning lives in the edges.A grammar for semantic graphs, argued in increasing depth from five rules you can apply tomorrow to a full positioning against schemas and vector search. It opens by insisting it is not a graph database pitch, and it publishes the four situations in which its own argument is the wrong one. ↗ v0.1.0What it argues → ↗ · Open graphs.sgit.ai ↗ ↗

infographics.sgit.aiThe brief is the argument. The infographic is one picture of it.A catalogue, not a generator: every rendered brief across the sgit.ai family in one place, each picture kept next to the argument it came from rather than circulating on its own.↗ v0.1.0Open infographics.sgit.ai ↗↗

issues-fs.sgit.aiThe issues are files. The files are a graph.An issue tracker with no database: nodes, edges and labels on disk, a small DSL, and a live graph derived from the repository itself. Ships a five-minutes-no-install lite mode for agents alongside the full model.↗ reference draftv0.1.2Open issues-fs.sgit.ai ↗↗

twins.sgit.aiA digital twin is an interface to reality, not a simulation of it.Twins as actors rather than models: what a working twin actually is, what was built versus designed, the simulation layer, and an execution broker. Carries its own gaps-and-open-questions page and a where-we-lose section.↗ v0.1.0Open twins.sgit.ai ↗↗

wardley-maps.sgit.aiMaps are claims, not pictures.Wardley mapping treated as graphs with position, so a map becomes something you can disagree with precisely. A 40-record doctrine assessment, the custom-axis verdict, the broken middle, and all 34 resources verified with dead links marked.↗ PROPOSEDv0.1.2Open wardley-maps.sgit.ai ↗↗

Security & infrastructure

pki.sgit.aiGood public key repositories existed, and were destroyedGood public key repositories existed and were destroyed. This site is the 2019 keyserver catastrophe, the four registry rules it produces, and the build order, all published before the registry exists, so the commitments are checkable against whatever eventually ships. ↗ v0.1.2What it argues → ↗ · Open pki.sgit.ai ↗↗

sg-compute.sgit.aiEphemeral environments in AWS, one command away.A serverless environment for agents: the machine surface, isolation and the one trade-off it makes, measured numbers rather than claims, and a clear what-ships-today line against the roadmap.↗ v0.2.0Open sg-compute.sgit.ai ↗↗

sg-sentinel.sgit.aiLayer 1 decides and signals. Layer 2 acts and writes.A design for an edge security and logging layer you own rather than rent, built on the observation that your own app already knows what a valid request looks like, so the edge can allowlist rather than denylist. Published as a complete design that has deliberately not been built. ↗ v0.1.1What it argues → ↗ · Open sg-sentinel.sgit.ai ↗↗

Business & publishing

influences.sgit.aiWhere the thinking came from.The sources behind this body of work, registered rather than gestured at, an influence map in three tiers, a register format, a changelog recording when a source moves between tiers, and a distinction between what was designed and what was discovered then confirmed.↗ v0.2.0Open influences.sgit.ai ↗↗

newsroom.sgit.aiThe story is a graph. The article is a projection.Provenance as the product: a worked story costed at £8.40, payment rails to the fact creator, micro and nano payments, CC-Signed content rights, and the roles an operating newsroom would need. A published design, not a running newsroom.↗ not builtv0.2.5Open newsroom.sgit.ai ↗↗

open-source.sgit.aiOpen source is a strategy. It is not a charity.Survivability as the test rather than licence purity: a stress test, a self-audit, six recorded corrections, six success stories with numbers, three licences compared, and why Apache-2.0 rather than MIT here.↗ draftv0.1.1Open open-source.sgit.ai ↗↗

subscriptions.sgit.aiA subscription is a discount for regular use, not rent on something you ignore.The commercial model stated as a position: a register of what you actually hold, governance and schema, an exit-path method, and the law behind it, with the service itself marked as later, not now.↗ draftv0.1.0Open subscriptions.sgit.ai ↗↗

Every site, at a glance

Read one in full

Four have a full write-up here, what the site argues, where it is honest about its limits, and why it is relevant to sgit:

• graphs.sgit.ai ↗, A node is just a node, meaning lives in the edges
• nhi.sgit.ai ↗, Agents you run, agents you rent, and the identity gap
• pki.sgit.ai ↗, A key registry for agents, designed from a documented failure
• sg-sentinel.sgit.ai ↗, An app-coupled edge guard, Layer 1 decides, Layer 2 acts

Why they are separate sites

Each one is an argument that needs room and a reader who arrived for it. Splitting them out keeps this site about sgit while letting each question be pursued properly, and gives each its own version history, release cadence and repository. They are built from the same generator and hold to the same rules, so a reader moving between them is not changing register.

This is also the refactor it looks like: material that would have made sgit.ai sprawl now has a better home, and this page is the index back into it. Adding the twentieth site is writing one markdown file.