An event on its own means very little
A raw signal is just a number with a timestamp. A derate, a proximity warning, a comms dropout: on their own they are alarms, and a site full of alarms is a site full of noise.
The classification layer is where a signal becomes a finding. Every normalised event is scored against the documents that govern your site, the SOPs, SWMS, permits and risk assessments, and against applicable Western Australian regulation.
Cited against your own sources
Classification is only useful if you can see why. Each classified event carries the sources behind it: the clause in the procedure, the regulatory reference, the prior event it matches.
That is what makes the output defensible. A finding is not the system's opinion, it is a citation back to your own documents and the regulation that applies, so a competent person can check the reasoning before acting.
From classified event to routed action
Once an event is classified and cited, the operating system correlates it with related events and routes it to the role that needs it, with the evidence attached and the audit trail recorded.
The classification layer never decides whether something is safe or unsafe. It produces cited evidence and a draft, and routes it to a human. The decision, and the responsibility, stay with the site team.