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

Reading room · threat-modeling.sgit.ai · llms-full

On this page

Reading room / threat-modeling.sgit.ai / llms-full.txt · section 1 of 19

threat-modeling.sgit.ai — a threat model is a claim about a system

A threat model is a claim about a system, and this site's job is to show claims being checked. It publishes the ThreatModCon 2025 vault (eleven linked threat models running Customer through Compute), a threat model that was validated line-by-line against the code that implements it, seven white papers arguing threat models should be machine-readable graph data rather than static documents, and the redacted method behind all of it.

Site version: v0.1.0 (8 September 2026). Written about, and published by, the estate whose own product it threat-models — participant disclosure at /about/participant.html. All site content CC BY 4.0.

The rule an agent consuming this site must inherit

Findings on the live product are published only once closed, dated, and classed — never by file-and-line location while still open. This site's own release gate refuses any page that looks like a source-file-and-line pointer outside the verbatim brief pack, and caps any quotation from a third party or a named framework (STRIDE, MITRE ATT&CK, CAPEC, CWE/CVE, OWASP Top 10, ASVS) at 40 words. Those frameworks are referenced and linked, never reproduced.

The spine: claim, then check

Every substantive page on this site carries the same two-part structure: what was claimed, and what checking it produced. /validated/ is the purest instance — a threat model written 16 March 2026, and a validation pass one day later that checked every finding against the actual code and recorded CONFIRMED REAL, CONFIRMED SAFE, CONFIRMED MISSING and N/A (proposed, no code yet) verdicts, publishing all four kinds rather than only the vindicated ones.

The pages

What this site does NOT do

No threat-modeling-as-a-service pitch on the main line — the services paper lives under /papers/ clearly labelled as positioning, not method. No open findings against live systems, including third parties. No methodology comparison table that declares a winner: the position is that fragmentation is solved by linking methods in a graph, not by picking one.

Properties an agent may rely on