GaitAI DefenceMotion
Movement intelligence for defence environments.
DefenceMotion configures SecureVision for defence installations: facility movement events for operator review, a gait-consistency signal beside existing credentials at controlled access points, and governed retention and audit across the same camera estate. It ships in Army, Navy and Air Force modes, which differ in the installation they are configured for rather than in what they claim.
Problem
Large installations find safety events after the fact, and controlled access rests on credentials alone — while the personnel being observed are owed a duty of care that identity-first monitoring does not respect.
What GaitAI does
Movement-first processing surfaces restricted-zone, perimeter and tailgating-like events on an operator timeline, and adds a passive gait-consistency indicator beside existing credentials for enrolled personnel only. Retention, roles, audit and skeleton-only processing are governed across all of it.
Operating modes
DefenceMotion is one module with 3 configurations. They differ in the installation they are set up for — the pipeline, the governance and the outputs are the same.
- Army ModeLand installations, barracks and vehicle depots
Perimeters, restricted compounds and vehicle movement areas, with controlled entry at stores and armouries.
- Navy ModeNaval bases, dockyards and shore establishments
Jetty and dockside zones, compartment access aboard alongside vessels, and gangway entry points.
- Air Force ModeAirbases, hangars and flight-line areas
Flight-line and apron boundaries, hangar and technical-area entry, and runway-adjacent restricted zones.
A mode is a configuration, not a separate product — the catalogue counts DefenceMotion once.
Who uses it
- Installation safety teams
- Base access control
- Programme and policy owners
- Oversight and audit functions
What they receive
Example report values — illustrative, not measured performance claims.
Events are indicators for a trained operator to review, and an access signal supplements existing credentials — it never identifies, admits or denies on its own. Escalation is a human decision under service procedure.
Why it matters
An installation's safety picture and its access picture are both movement questions, and answering them without identity-first monitoring is what makes them answerable at all in an environment with a duty of care to the people in frame.
Example workflow
- 01Zones, perimeters and access points are configured under the programme owner's policy
- 02Facility movement events surface on the operator timeline
- 03Controlled entries receive a consistency indicator beside existing credentials, for enrolled personnel only
- 04Safety and access teams review and decide under service procedures
- 05Every indicator, review and access is recorded in the audit trail
Deployment
- On-premise or edge processing inside the installation's own network
- Consent-based enrolment wherever an access signal is used
- Human review before any indicator becomes an action
- Not designed for autonomous targeting or lethal decision-making
Evidence status
GaitAI Evidence Index
1 categories documented
What is documented for this module, and what is not. Research foundation is not product validation — the two are listed separately on purpose.
- Research foundationNot yet published
- No published record in this library directly addresses a capability this module is built on.
View evidence for Research foundation
Claim / capability: No published record in this library directly addresses a capability this module is built on.
Status: Not yet published
Applicability: The cited work is specifically about a method or movement signal this module draws on.
Limitation: Research relevance is not evidence that this product's outputs have been validated.
No supporting source is published for this status.
Inventory reviewed .
- Architectural research relationshipNot yet published
- No further shared-platform research relationship is recorded beyond the research foundation above.
View evidence for Architectural research relationship
Claim / capability: No further shared-platform research relationship is recorded beyond the research foundation above.
Status: Not yet published
Applicability: Shared capabilities such as pose estimation or temporal modelling are used by many modules.
Limitation: A shared-platform relationship is the weakest research link and must not be read as validating this module.
No supporting source is published for this status.
Inventory reviewed .
- Product specificationAvailable
- The module has a documented specification: inputs, pipeline, outputs and stated limitations.
View evidence for Product specification
Claim / capability: The module has a documented specification: inputs, pipeline, outputs and stated limitations.
Status: Available
Applicability: Documented inputs, intended workflow and output design.
Limitation: Documentation does not establish a released implementation or deployment readiness.
- specificationProduct documentation
Inventory reviewed .
- Product implementation evidenceNot yet published
- No module-specific release or deployment record is published here.
View evidence for Product implementation evidence
Claim / capability: No module-specific release or deployment record is published here.
Status: Not yet published
Applicability: Production implementation is distinct from this website's interactive prototypes.
Limitation: The browser pose explorer is not the full clinical or operational product pipeline.
- Context · not validation evidenceProduct and deployment context
Inventory reviewed .
- Interactive demoNot yet published
- No sample output has been built for this module yet.
View evidence for Interactive demo
Claim / capability: No sample output has been built for this module yet.
Status: Not yet published
Applicability: An interactive explanation of the intended output and workflow.
Limitation: Sample outputs contain illustrative values and are not measurements of a visitor or product performance.
No supporting source is published for this status.
Inventory reviewed .
- Benchmark validationNot yet published
- Validation pending publication. No product benchmark numbers are supplied.
View evidence for Benchmark validation
Claim / capability: Validation pending publication. No product benchmark numbers are supplied.
Status: Not yet published
Applicability: A benchmark needs a defined dataset, sample count, environment, hardware and evaluation method.
Limitation: Accuracy, sensitivity, specificity, latency and FPS cannot be inferred from a demonstration.
- Context · not validation evidenceResearch evidence inventory
Inventory reviewed .
- Product-specific validationNot yet published
- No study in the published record evaluates this module's output for a particular intended use.
View evidence for Product-specific validation
Claim / capability: No study in the published record evaluates this module's output for a particular intended use.
Status: Not yet published
Applicability: Validation must match the module, population and intended decision.
Limitation: A product description or related research paper does not establish validated performance.
- Context · not validation evidencePublished evidence inventory
Inventory reviewed .
- Pilot & deployment evidenceNot yet published
- No named pilot, deployment result or customer outcome is documented.
View evidence for Pilot & deployment evidence
Claim / capability: No named pilot, deployment result or customer outcome is documented.
Status: Not yet published
Applicability: Pilot and deployment evidence is assessed separately from research.
Limitation: Use-case journeys describe intended workflows, not customer results.
- Context · not validation evidenceTrust Center
Inventory reviewed .
- Product-specific clinical validationNot yet published
- No product-specific clinical validation study is published in this library.
View evidence for Product-specific clinical validation
Claim / capability: No product-specific clinical validation study is published in this library.
Status: Not yet published
Applicability: Clinical applicability depends on the intended use; safety modules are not presented as clinical tools.
Limitation: No output replaces clinician judgement or establishes a diagnosis.
- Context · not validation evidenceResponsible use and intended context
Inventory reviewed .
- Regulatory clearanceNot claimed
- No medical-device clearance, regulatory approval or compliance status is claimed.
View evidence for Regulatory clearance
Claim / capability: No medical-device clearance, regulatory approval or compliance status is claimed.
Status: Not claimed
Applicability: Regulatory applicability depends on the intended use and deployment jurisdiction.
Limitation: Research publications, patents and prototypes are not regulatory clearances.
- Context · not validation evidenceWhat GaitAI does not claim
Inventory reviewed .
Inventory reviewed How GaitAI states evidence →
Privacy & responsible use
Responsible deployment: DefenceMotion is human-supervised throughout. It is not designed for autonomous targeting or lethal decision-making; an access signal supplements existing credentials and never identifies or denies on its own. No defence deployment, customer or clearance is documented. Designed to support consent-based capture, encrypted transfer, configurable retention and role-based access, with activity logging and skeleton-only processing modes. Deployment requirements depend on the applicable environment, organization and jurisdiction. Privacy-aware architecture does not automatically mean anonymity: pose, gait and trajectories may still carry identifying information. Movement analytics are designed to run without identifying individuals unless a deployment lawfully and explicitly requires it, and identity-related capabilities are intended only for lawful, authorized deployments with appropriate governance, access control and auditability. Outputs are decision support for trained operators — not autonomous enforcement.
Context & limitations
- Indicators are not identity proof and are not admission decisions
- Access signalling requires consent-based enrolment and covers enrolled personnel only
- Not designed for autonomous targeting or lethal decision-making
- No defence deployment, customer or clearance is documented
Related SecureVision products
All products
Anomalies surfaced — without identity matching as a prerequisite.
Surfaces candidate movement events — loitering, running, restricted-zone entry, tailgating-like patterns and perimeter events — for operator review, without requiring identity recognition.
A passive second factor — your walk.
Contributes a passive gait-consistency signal alongside card, face or mobile authentication in high-security spaces. It supports an existing credential rather than replacing it.
Movement intelligence — with task-relevant movement representations.
The architectural privacy layer for GaitAI: designed to support skeleton-only analytics, face blur, role-based access, configurable retention and audit logs in privacy-sensitive environments.