standards.sgit.ai / instruments / iso-31000

ISO 31000 Standard

There is nothing here yet, and this page is one paragraph explaining why rather than two thousand newly-written words pretending to be a consolidation.

Kind
Standard — ISO 31000 (risk management) and ISO/IEC 27005 (information security risk)
Republishable
NO — the same ISO constraint as 27001
In the source corpus
Zero occurrences. Verified case-insensitively, with and without spaces and slashes
Status
Not started, and deliberately not stubbed with generated content
Where the risk work is
risks.sgit.ai

Nothing exists, and that is the finding

ISO 31000 and ISO/IEC 27005 were named in the commission for this site. Neither appears anywhere in the material behind it — zero occurrences, checked case-insensitively and in every spacing and punctuation variant. There is no analysis to publish, nothing to adapt, and no worked example to lift. Writing a page anyway would mean generating an account of a standard nobody here has worked with, which is the exact failure mode this site exists to argue against: second-hand content presented as though it points at something. And the text could not be quoted even then.

What is almost certainly wanted instead

The reason to reach for “the risk standard” is usually a wish for the apparatus, not the document — a way to say what a risk is, when it is grounded, and what accepting one means. That apparatus exists in this project, it is substantial, and it is a different site.

The site

risks.sgit.ai

The register, the acceptance decision, RAMM, and the distinction that does most of the work: accepted is not the same as acceptable.

Go →
Shared

The grounding ladder

Five lines defining what must exist below a claim for it to stand. Shared apparatus — this site owns its application to provisions, risks owns its application to the register.

Read →

The boundary, stated so neither site rebuilds the other: risks owns the register and the acceptance decision; standards owns the provision and the arithmetic. Where a worked example serves both — and one does — there is one canonical copy and the other links in. Q1, open →

If this folder is ever built

It would be a 27001-shaped folder: clause references, the project's own interpretations, a reading guide, crosswalks to publishable instruments, and an empty source/ layer. The prerequisite is the same open question — whether the model can hold a standard it cannot quote — and the honest sequencing is that it comes after instruments that can be quoted, because those are the ones that establish whether the method works at all.