All 42 concepts, addressable

C1 Risk acceptance as underwriting, not prediction #c1

A risk is not a probability estimate about a future event but an exposure that already exists, which a named person underwrites insurance-style for a stated interval, with accountability attached.

The founding inversion. Traditional risk management predicts the probability of a future event; this model asks a named human to underwrite an exposure that already exists. It relocates the discipline from actuarial estimation to accountable ownership, and it is the reason the rest hangs together: once someone must sign, they demand evidence, which manufactures the demand for the grounding ladder underneath.

“we are not describing the risk of something happening, we are asking them to accept it, to underwrite it”

C2 The no-deny mechanic #c2

A risk with a real vulnerability under it exists whether or not anyone acknowledges it, so there is no deny button — the only choice is how long you accept it before re-accepting.

The single most distinctive primitive. Denial in conventional registers is a fiction that only works while the risk has not materialised; removing it converts risk management from a gate into a forcing function. What replaces denial is three moves — accept, escalate, or challenge the fact — so the person is routed rather than cornered.

“the mistake of a lot of risk registers is that they allow the risk to be denied, which can only happen when the risk has not materialised”

C3 The acceptance interval ladder #c3

The interval is not metadata about the decision — the interval IS the decision, because each rung implies a specific operational response and therefore a specific cost. Six rungs: 1h, 4h, 1d, 1w, 1m, 6m, default one month.

Choosing a duration sets severity and commits resources in the same click. Under 24 hours means pull the plug; a day to a week is a lower-grade incident; a week to a month is a project for an existing team; one to three months means assemble and fund; over three months means you are waiting to see, which is legitimate if said out loud. Rungs that are physically impossible are struck off before the choice is offered.

“if you have less than a day risk acceptance, then that is fundamentally a P1, because if you say I do not want to accept this risk for more than an hour once I know about it, then that means you need to pull the plug”

C4 Unaccepted equals critical #c4

A risk nobody has accepted has not gone away — it rests on whoever is nearest, so it is rated critical by default and rolls upward without anyone choosing to escalate it.

The sharpest inversion of incentives in the corpus. In most organisations a risk nobody escalated feels safest to the person holding it; here it is the worst state available, because that person is personally carrying an enterprise exposure with no signature above them. It is aimed at attrition rather than refusal: it removes the deniability non-participation depends on, without requiring anyone to cooperate.

“that person right now is accountable for the business, which is very bad from a business point of view, but is also very bad for the individual”

C5 Accepted is not acceptable #c5

Two orthogonal axes, not two stages. Accepted is an act by a named person at a dated moment; acceptable is a threshold the business owns — the moment it is happy to stop funding remediation.

The vocabulary correction that turns risk appetite into something computable, producing four quadrants each requiring a different response. Acceptable is risk appetite renamed, and renaming it makes it operational because the instruction that matters most is the one that stops work. EU AI Act Article 9(5) requires residual risk to be judged acceptable and never defines the word — so the obligation to judge is imposed and the standard is not supplied.

“the acceptable risk is the moment that the business is happy to stop funding remediation activities”

C6 The grounding ladder #c6

Reality → Twin → Measure → Evidence → Fact → Vulnerability → Risk → Top Risk. Every node type is defined by its required paths; downward paths ground, upward paths classify.

The definitional spine of the corpus, and the concept agents most need. A Vulnerability is simply a Fact with an upward path to a Risk. A Measure is NOT the floor — it is grounded further in a Twin and through it in Reality. The floor is a stopping test: the last node where going deeper would neither improve observability nor change a decision.

“A Fact becomes a Vulnerability purely because of its upward link to a Risk, so that legitimacy is conferred entirely from above”

C7 Node type formulas #c7

What a node IS should be computed against the graph rather than decided in a classifier's head. A node type is a required pattern of typed, directed paths, so classification is a query.

Classification becomes dynamic and path-relative — promotion and demotion are edge events. Bias does not disappear; it moves out of the classifier's head into the formula, where it is visible, versioned and arguable. Two parties who disagree stop trading intuitions and start diffing formulas. The formula LANGUAGE is undefined and nothing executes a formula.

“the ontology definition of a node type is its upward and downward path-pattern, not a sentence about what it contains”

C8 Ontologies of ontologies — bridges, not merges #c8

Multiple parties each own their own formula over a shared factual graph, connected at declared crosswalk points rather than merged into one schema.

A node can be a vulnerability under one formula and not another, and both are valid — they are different queries over the same graph. The worked proof is a security-centric formula (System, Fault, Security Failure, Conditions) which turns out to be a sub-path of the business-centric one: its Security Failure plays exactly the structural role of the promotion edge, differing only in terminus.

“We do not fold their definition into ours, which would erase the security-centric view that is the whole point of having it. We declare a bridge: a Security Failure gives rise to a Business Risk”

C9 The risk register as a graph of graphs #c9

The register is a hyperlinked semantic graph rather than a spreadsheet, and it begins where scanners stop — at the vulnerability — mapping accepting, funding, and finding who does the work.

Buildable now because vaults supply the storage and hyperlink layer and PKI solves attribution. Its distinguishing move is where it starts: most security products end at the vulnerability, and everything expensive happens after that point.

“a lot of security teams and products end on the vulnerability, and what I want to show is the multiple layers involved in fixing it, but even before that, in accepting the risk, funding the solution, and finding who is going to do it”

C10 Fractal risk registers #c10

Wherever there is a stakeholder who accepts a risk there must be a register — company, department, role. Only the role's own register is stored; the rest are queries.

A person's register is all the risks that bubble up to them, derived rather than curated. An individual has at least two and often three: their role-specific register in their own domain language, plus derived views of the registers above.

C11 Relevance fade #c11

Centre a view on a role: that role's register is lit in full, and the registers above fade except for the entries that trace back down to it — which turns the register into an education mechanism.

A database administrator can see that their local “an agent holds unrestricted access to a customer table” is the same object as the board's “regulatory penalty, loss of licence, continuity failure”. Seeing that once teaches more than any training course. The visualisation is described and has not been built.

“as you go up, imagine the colours can fade away for the next registers for the bits that are not relevant, so the graph starts to point which parts of the risk register above are relevant to this individual”

C12 Registers are one chain, not parallel lists #c12

Three altitude registers drawn side by side demonstrate a formatting capability; drawn as one chain rooted in an existence fact they demonstrate the entire thesis.

The CISO's risk exists BECAUSE OF the operator's risk, which exists because of a fact stating an agent touches production. Drawn side by side that dependency is invisible; drawn as a chain it is the point. A late and consequential correction.

“at the moment it looks like the cards, they look side by side, and it's actually not that”

C13 Technical owner versus business owner #c13

The technical owner validates that the vulnerability exists; the business owner owns and accepts the risk it gives rise to. Conflating them is the canonical governance failure.

IT validating a 2FA gap is not IT accepting an HR data-breach exposure. The model's response to the confusion is not to reject the acceptance but to make the misplacement a rateable risk of its own — the governance air gap.

“most of IT should be technical owners of something, but the business owners are the ones that actually own the risk”

C14 Confirmed, validated, accepted — the three-predicate model #c14

Three distinct acts held by three distinct roles, tracked per risk per altitude. Confirmed is factual, validated is interpretive, accepted is a judgement about appetite.

The interesting cases are the mismatches: a risk accepted by an executive but never confirmed is an acceptance of something that may not be true. A single status field cannot express any of them.

“we probably also want the GRC person to validate the risks, especially to do with the compliance element”

C15 The underwriting graph and propagation to the board #c15

An exec never decides alone: the direct-line owner, the CSO and at least GRC must each have recorded an acceptance or an explicit refusal before an executive acts. Then it propagates upward.

A recorded refusal counts as much as a recorded acceptance. Once accepted at the right altitude it propagates to the boss, the boss's boss and the CEO, who acts for the board, with the largest going to the board itself. Superiors may override in either direction, with the original acceptance preserved and the override attributed — though no authority model for override is stated.

“the exec should never make a decision that has not been underwritten by the relevant player”

C16 Cascade and the air gap #c16

Every change to any risk, fact or evidence must trigger a cascade to the top. The absence of a cascade is an air gap — and so is a risk that exists in the business but is not connected to the register.

Registers with air gaps silently drift out of date and the business decides on bad data. Cascade works in both directions: a risk appearing propagates up, and a risk resolving propagates up too, clearing it from the board's view. Detecting air gaps is an acknowledged open problem.

“every time any risk, any fact, any evidence changes, you have to trigger a cascade that reaches the top. If you do not have that, you have an air gap”

C17 Not knowing is a fact #c17

Absence of evidence is a first-class node. A measure can be a documented zero, and an unevidenced fact is recorded as unevidenced rather than left blank — which makes it countable, queryable and assignable.

Gaps in knowledge spawn their own risks. Questions become their own node type, and unanswered question nodes are the most productive output of the whole exercise. Rendered convention: amber is exposure, green is assurance, ghosted is unanswered.

“not knowing a fact is also a fact. Lack of evidence is also evidence, because then we say we do not know, and somebody needs to investigate until we do”

C18 CIA blast-radius expansion #c18

From a single risk, expand through confidentiality, integrity and availability — each branch spawning its own risks, each following the full validate-accept-propagate loop.

A leak splits into two distinct risks with different owners: the CFO's, for the fine, and the CEO's, for the compliance failure — and inadequate protection may already be a breach. Integrity is the under-modelled axis because it produces no alert. Availability terminates in the question that reliably produces the worst answer: when was a restore last tested? The expansion must be curated, not exhaustive, or it blows up combinatorially.

C19 Blast radius and authorization closure #c19

An agent's real authorization is the transitive union of everything reachable from what it was given, not the nominal grant — and not what it did. Compute it; do not assert it.

Two awareness gaps hide the delta: the granter does not know the full scope of what it grants, and the original delegator never authorised re-delegation. Inbox access is access to every account resettable by email; desktop access is every stored credential and live session; code execution escalates. The key quantity is the delta between expected and unexpected permissions.

“at the end of the day you are still accountable for those actions, all the way to the board”

C20 Who can pull the plug — two symmetric risks #c20

If nobody holds the mandate to stop an AI system that is one risk; if the system cannot be stopped when someone decides to, that is a second and different one. An authority gap versus a capability gap.

The second is widely underestimated. It decomposes into timed sub-risks — can it be stopped in an hour, ten hours, a day, five days; only in office hours — which turns governance into an on-call availability problem, including whether the person can act without fear of losing their job.

“if you do not have somebody who has the mandate to pull the plug, you have a risk, and if you do not have a system that can be pulled the plug, you have a risk too”

C21 The four-way time intersection #c21

Detection, decision, blast radius and reversibility must all line up inside the same window. A gap in any one breaks the whole thing.

Detection is a curve, not a binary. Decision is whether the authorised people can be assembled in time. Blast radius is steep because models execute and scale fast. Reversibility is the half people forget — stopping is only half the act. The danger case is an affordable window of one or two days of damage colliding with a decision that cannot be made in one or two days.

“it is not just pulling the plug, it is pulling the plug and reverting the changes”

C22 The five-dimension plug profile, and the “no plug” correction #c22

The plug ALWAYS exists — you can always disconnect, revoke or shut down. What older registers recorded as “no plug” was zero recoverability. The profile carries who holds it, blast radius, speed, side effects and recoverability.

Restating a blank as a profile turns a frightening dead end into an ownable finding that points at prevention and the most senior acceptance. A blank is unassignable and unfundable; a profile has an owner, an altitude and an interval.

“The blank said stop looking. The corrected profile says here is exactly what to do”

C23 Recoverability as the hard limit #c23

The dimension money cannot buy back, and the one that stops irreversible harm disappearing into an expected-loss calculation. The flagship query: show me every accepted risk whose recoverability is zero.

An organisation that can run that query and read a short, deliberate, senior-owned list is in control of its worst exposure; one that cannot is accepting its irreversible risks by default and by silence. The small-but-permanent quadrant is the one the model exists to surface. Scoring recoverability — grading the partially recoverable middle — is an open question.

“The money can be refunded; the customer cannot be un-declined”

C24 Altitude #c24

Organisational elevation as a first-class modelling dimension: a risk is accepted at the right altitude and then propagates, is restated in each altitude's own language, and has a different plug at every level.

Five levels appear in the worked examples: L1 endpoint/IT, L2 security, L3 business, L4 enterprise, L5 board. A risk may be confirmed at one altitude and accepted at another, which is why confirmed, validated and accepted are tracked per altitude.

“this is very important, the multiple altitudes of the risk register, because there might be risks that are only accepted at certain altitudes, or might be risks that are only confirmed at certain altitudes”

C25 Risk appetite as a revealed band #c25

Appetite is a band rather than a number, a fractal network of bands rather than one figure, and discovered rather than declared — computed from what the business paid to reduce and every fresh acceptance.

The target is to operate inside the band: above it you are buying risk the owners will not underwrite; below it you add attrition and slowness for nothing. The gap between declared and revealed appetite is the finding.

“risk appetite is that band, that interval between two numbers, if you think of zero to one hundred in terms of risk, it is a spectrum, and it can be wider or shorter”

C26 The psychology of the physical act #c26

The click, the emoji, the signature is the moment a decision stops being ambient and becomes something a named person did, at a known time, on known information.

Without it, declining decays into a non-event: someone says “I'm not comfortable” and nothing happens. Accountability follows the act, and eventually liability, as it should — and the prospect of signing concentrates executive attention in a way dashboards never do.

“suddenly the executives ask good questions, they really engage, they get a level of focus that just was not there before”

C27 Accept first, then adjust the level — the risk level ledger #c27

For a risk you already have facts for, the first move is universal stakeholder acceptance at its current level. From there the level is a dated ledger of adjustments, each re-accepted.

Adjustments are triggered by one of three things: new data, a funded project, or an incident. Re-rating up after discovery is honesty rather than failure — the risk did not worsen, the estimate improved. It sits awkwardly with the no-deny mechanic: if the level can be adjusted after acceptance, denial has a route back in.

“you literally cannot mitigate what you cannot count, and the only honest first step is to accept, now, that an unknown and largely over-permissioned population of agents holds access to the enterprise's assets”

C28 Everything has risks — register density and calibration by surprise #c28

A risk is the unintended side effect of a capability, so anything that does something has risks. A complex product should have dozens to thousands of interconnected risks.

Capabilities exceed features, and undocumented capabilities are where unowned risks live. The diagnostic: a listed risk materialising is expected; an UNLISTED risk materialising is the real alarm, because it raises two questions — why was it missed, and what else was missed?

C29 Risks that cannot be fully mitigated #c29

Mitigation lowers likelihood or impact but cannot reach zero for structural reasons, so a material residual always remains and must be owned. Demanding zero produces covert acceptance.

Agentic AI's residual is today irreducible: prompt injection, emergence, non-determinism, reach, model supply chain. Some harms are irreversible, and compliance reduces but does not remove liability. Covert acceptance is strictly worse than an owned residual — identical exposure, nobody's name on it.

C30 Meta-risks — the risk about your risk management #c30

A recurring family: not knowing how many agents you have, not having defined an acceptable level, a risk accepted by the wrong person, and systematic downgrading across a business unit.

Each is a gap in the governance apparatus, stated as a rateable risk with an owner and an interval — which triggers and funds the work that closes it. External anchors defeat systematic downgrading, because an internal severity is an opinion while an external requirement is not.

“we are the meta risk; we allow the creation of the project that is going to discover this and that funds this”

C31 The register maintains itself #c31

Accountability manufactures the demand for evidence, so no separate data-quality function is required. Anticipated review converts care into a demand for evidence before the decision.

Three primitives produce it: the risk already exists, it attaches to a named person, and the decision is reviewed upward. Three named failure conditions: the reviewer's preference being guessable, commitment to a prior position, and broadened information appetite without improved discrimination.

C32 Three moves, none of which is denial #c32

Accept for a stated interval, escalate (this is not mine to accept), or challenge the fact itself. The person is routed rather than cornered.

The reconciliation of the no-deny primitive with human reactance: presenting a single button to a person who feels they have no alternative produces counter-argument and resentment, not compliance. The absence of a reject option should be discovered, not announced.

C33 Decision as a first-class node #c33

An acceptance is a separate object, not a field on a risk — which is what allows many dated decisions per risk, one decision covering several risks, and a calibration record.

The calibration record is the point: over time you can ask whether the person who accepted for a month was right. That question is unanswerable if the decision was a field that got overwritten.

“a decision is actually captured independently from the risk”

C34 A question is not a risk #c34

If a sentence cannot sensibly carry a named acceptor and an interval, it is not a risk and does not belong in the register. Questions become their own node type.

“Nobody accepts ‘whose call is it at three in the morning' for six months.” A clean quality gate, and one of the few things in the corpus that can be applied mechanically. Unanswered question nodes are the most productive output of the whole exercise.

C35 Do not internalise the risk #c35

Risk professionals frequently internalise exposures the business decided to carry, at real personal cost. The workflow relocates accountability to where authority already sits.

The corpus cites survey data of 63–76% of security leaders experiencing or witnessing burnout in a single year, and names accountability-without-authority as the defining pressure. The standard remedy — give the security leader more authority — is correct and rarely achievable; this solves the same equation from the other side. Nothing is taken from anyone; the register records what was always true.

“I would see the risk professionals almost own the risk; they almost take it personally with the risks that the business was taking, and it was a massive source of stress”

C36 The evidence economy — force of proof and the fact certifier #c36

Once executives are personally accountable and the graph traces their statement to the evidence beneath it, demand for correct evidence becomes cheap to make and impossible to wave away.

This splits the register into two separately liable roles: the risk-acceptor, who owns the decision and its consequence, and the fact-certifier, who owns the truth of the inputs and sells a correctness guarantee. A wide confidence band converts unease into a purchase order for better evidence. Risk owns the demand side; the supply side belongs to newsroom.sgit.ai.

C37 Confidence bands and margin of error #c37

Confidence is a first-class property of every node. A rating needs a band, not a point, and the band is widest where the data is thin.

A band too wide for comfort triggers the get-more-data direction; a band spanning trivial to catastrophic cannot be accepted responsibly. Confidence propagates across the graph like risk, and “we don't know” is the widest band.

C38 Two underwritings — decision accountability versus factual accuracy #c38

The domain expert underwrites that a fact is true and fit for the use being made of it; the business owner underwrites the decision. Both are required.

Every graph traversal adds an abstraction layer that strips detail and drifts weight, so the signature failure is a component used beyond what its owner would underwrite. Decision accountability is only legitimate if the data underneath it is correct.

C39 Observability as a risk dimension #c39

Capability maps the privilege; observability maps the real impact. A loud, detectable, slowly-scaling, well-drilled risk is lower than a quiet, fast, unwatched one of the same capability.

Six objective vectors on a maturity scale: capture granularity, log latency, time-to-damage given real throughput limits, whether monitoring is actually on and watched, whether there is a team with playbooks, and whether detection has been drilled. Later sharpened into plug-loaded observability — logs that tell you where you are in the stopping decision.

C40 Five whys as a domain translator #c40

Not a root-cause tool but a translator that moves a statement from one domain into another — as many whys as it takes to reach the top of a domain.

The graph has natural peaks: on risk it converges to the single risk of staying in business, and because it converges a legitimate single number can be carried to the top. Aimed downward, the same chain captures the second, third and fourth stories — the root causes.

C41 Digital twins and the discipline of reality #c41

The twin is where the graph stops modelling and continues into a real system — the grounding point beneath every measure. A twin not connected to reality is a tracked air gap.

How connected a twin is to reality is itself a measurable property, which introduces a useful recursion: trust in a measure depends on the twin's connectedness, and that connectedness is itself a measure. Twins in their GENERAL form belong to graphs.sgit.ai; what is risk's own is the twin as the grounding point of the ladder.

C42 The narrative engine — the register as story #c42

The register is meant to be experienced as a story rather than read as a spreadsheet: replay the change history so the analyst watches the risks propagate and settle.

The commit log is the script; the query advances the scene. The analyst watches the vulnerability appear, risks propagate, a governance risk fire and resolve, the blast radius bloom, and everything settle into the board's consolidated view. The mechanism is undecided in the source document.

“I want to show this story played as a narrative, almost like a football commentator, this happens and then that happens, almost like a whodunit, like investigative journalism”