In developmentDefence

Neura Angrakshak

Framework Karan

The framework is called Karan

Police, navy, air force. The work of protecting a country and the people in it, looked at through one measure that is rarely used: how many lives ended, counting every side.

In almost every one of these situations, somebody dies. Usually more than one.

A police officer. A civilian who was simply present. The person on the other side of it, who in most cases someone was waiting for at home as well.

The standard applied afterwards is whether the operation succeeded. That is a real measure and it matters. It is also incomplete in exactly the way a crash rating is incomplete: it describes the outcome without asking whether the outcome had to include the deaths.

Karan takes the harder measure. Not zero incidents, which nobody can promise. Zero deaths, on every side. A target you will miss, held anyway, because the alternative is treating the count as a cost of doing the work.

What we would argue for.

This is a consulting position, offered to forces and agencies that already hold themselves to a high standard and know where the remaining gaps are. We build nothing and supply nothing.

See the whole situation, sooner

Most escalation happens because the people arriving know less than the people already there. Better information earlier is the cheapest life-saving intervention available.

Distance as a design goal

Every metre and every second between the parties involved is an option that did not have to be taken. Systems should be creating those, not closing them.

De-escalation as a measured outcome

If nothing in the system records the incidents that ended without harm, the organisation cannot learn from its own best work.

Protect the responder too

An officer who is safer is an officer with more room to make a considered decision. Their protection and everyone else's are the same problem.

Account for it honestly

Counting every life lost, including the one nobody wants to count, is the only version of this measure that means anything.

Neura Angrakshak is in development.

A sector where nothing should be claimed lightly and nothing should be built without the people who do the work. We consult, and take a 1% equity stake in the outcome instead of a fee.

Straight answers

What does zero deaths mean here?

Zero deaths on every side. An officer, a civilian, and the person on the other side of it.

Is that realistic?

Zero incidents is not, and pretending otherwise is dishonest. Zero deaths is a different target and it is the one worth designing against.

Is this about equipment?

No. We build nothing and supply nothing. This is a direction we would consult on.

Why count the attacker?

Because a standard that counts one group and not another is not measuring safety. Somebody was waiting for them at home too.

Is this in development?

Yes.

Five things worth knowing

01
Most of the risk in an operation is created in the minutes before contact, by people acting on partial information.
02
If the only well-supported option is force, force becomes the default.
03
A tired person on hour fourteen makes different decisions. That is a safety question, not an HR one.
04
Civilians in the vicinity are rarely part of the operational model until afterwards.
05
A system that cannot review itself honestly cannot improve.

One question

Should a defence standard count every life lost, on every side?

One vote per visitor

Tell me where I am wrong

Two fields. Name the problem, then say where you think the resolution sits. Nothing publishes until it is read.