Business continuity
Somewhere in your organisation there is a critical task only one person knows how to run. Nothing about today tells you which one. You find out the week they are unavailable — and by then the question is not who knew, it is who can.
What a skill actually is
And they are not limited to what people use in their formal day-to-day. A skill is everything a person knows how to do, can solve, teach, operate, improve, or recover when something goes wrong.
That distinction is why this is modellable at all.
as an attribute
A diploma sits on a person and connects to nothing. It is a claim about the past, typed once, and no work in the organisation depends on it.
as a relationship
An ability is held, required and improved — three edges that exist whether or not anybody writes a profile.
Once it is a relationship, it can be counted.
Today · invisible
Ren J Ishikawa-Reed — a Person, acting as Actor — executes Specialized Paint. It requires Metallic Basecoat Application, a technical skill held by him and by nobody else in the organisation.
knows the person
knows the process
knows the judgement
Every one of those three facts is known. Bus factor: 1 is not written anywhere, because it is not a fact about any of them — it is a fact about the path.
People
Ren J Ishikawa-Reed
Process
Specialized Paint
Technical Skill
Metallic Basecoat Application
People
Ren J Ishikawa-Reed
Technical Skill · held by 1
Metallic Basecoat Application
This is what people mean when they say the risk was hiding in plain sight. Nothing was hidden. Nothing was joined.
Many companies discover too late that they had a deep fragility in how they managed people, knowledge and processes. The problem never shows up while everything works. It shows up the moment the only person who knew how is no longer available.
Answerable
Which critical tasks rest on a single person?
Because people, tasks and skills are typed nodes joined by real relationships, a single point of failure is not a discovery. It is a traversal — and it returns a list.
the list it returns · bus factor = 1
→
Specialized Paint — Ren J Ishikawa-Reed · Metallic Basecoat Application, held by 1
→
362 purchase orders — Annette L Hill · no secondary assignee
You could get that list from a survey. You would get it once, it would take six weeks, and it would be wrong the following Monday — because the answer changes when someone moves team, and nobody files a form for that.
A traversal is not a report you commission. It is the current state, computed the moment you ask.
Mitigate
A Recovery runbook — a Knowledge node — improves the skill. A second person is cross-trained and now holds it too. Bus factor rises from one to two, and it rises on the record: not in a slide reporting that training happened, but as a relationship that changes the answer to the query.
Knowledge
Recovery runbook
Technical Skill
Metallic Basecoat Application
People
2 holders
That is the part most continuity programmes never reach. Finding the risk is a project. Proving you closed it is usually a promise. Here it is the same traversal, returning a different result.
Monitored
Continuity risk does not arrive. It drifts. Someone changes team, someone hands over half a responsibility, someone leaves and the cross-trained colleague left three months earlier. No event fires. Every one of those movements changes the answer, and none of them prompts anyone to recompute it.
A typed graph with lifecycle state is something an agent can watch. So the flag comes to you: this task just dropped to a single holder — escalated to the role accountable for it, because the model knows who that is.
01
Detected
02
Routed
03
Decided by a person
04
Recorded
Continuity risk does not arrive. It drifts.
Autonomy of attention, not of authority. The agent identifies, reports and escalates — and continuity is the case where attention is the whole value.
What it takes
There is no inference trick here. If Metallic Basecoat Application was never modelled as a skill, no traversal will find it. Continuity coverage is exactly as good as the part of the organisation you have typed.
Which is why this does not start with an inventory of everyone's abilities. It starts with the tasks you already know are critical — usually a couple of dozen — and works backwards to the skills they require and the people who hold them. That is a week of work with the people who run those tasks, not a framework to roll out.
From there it grows the way the rest of the model grows: every node independently lifecycle-managed, so a partial map is already answering the question for the part that is mapped.
Already modelled
Ren J Ishikawa-Reed, Specialized Paint, the skill held by exactly one person, and the query that flags it — already in the model you can open right now. Run the traversal against an organisation that is not yours, then decide whether you want the same answer about your own.