EVIDENCE

Evidence you can inspect

Evidence should identify the function, conditions, date, method and limitations. A demonstration is not a measured customer result.

Evidence statusReviewed 2026-09-19

Approved deployment evidence

No approved PGAK customer result or measured accuracy report is attached to this release. Published scenarios are illustrations, not verified deployments.

No customer footage, product interface or measured result is presented here as approved evidence. Third-party reference clips used in the earlier design are excluded from this buying journey.

What a useful demonstration should establish

  • The supported function and exact software/processing configuration.
  • The source of the scene: customer deployment, permissioned lab test or illustration.
  • Camera/firmware settings, site conditions and relevant constraints.
  • What the operator sees, the evidence format, recipient and handling process.
  • False alerts, missed events and failures, with a denominator and test method for any measurement.
Use the test worksheet →

Illustrative deployment scenarios

The existing scenarios explain a possible approach. They are separate from verified customer results.

Read labelled scenarios →

Architecture illustration record

Illustration19 September 2026

From a camera feed to human review

A proposed operating architecture, shown on the homepage. No live PGAK interface or customer footage is used.

Conditions
Conceptual drawing only. Stream, processing, evidence and response steps require technical verification.
Limitations
Does not establish implementation, compatibility, detection accuracy, notification channels or customer outcomes.
Text description / transcript
A compatible stream is assessed; processing and rules are scoped; event evidence and delivery are tested; an authorised person owns the response.