robodog-defensive-systems-lab

Table of Contents

• Safety and Publication Boundary
• Overview
• What This Repository Is
• What This Repository Is Not
• Relationship to Other Projects
• Architecture
• Technology Stack
• Current Status
• Compliance and Export-Control Notice
• Roadmap
  • v0.1 - Foundation
  • v0.2 - Core Technologies
  • v0.3 - Integration
• License and Use Policy
• Authors
• Acknowledgments

Defensive spectrum-awareness, secure coordination, and autonomy-safety research.

Safety and Publication Boundary

This repository is intentionally limited to non-operational research artifacts:

• synthetic data only;

• no real RF captures;

• no operational jamming procedures;

• no target-selection, tracking, or surveillance workflows;

• no weapon-control or payload-control logic;

• no instructions for unlawful interference with communications;

• no deployment guidance for military or restricted end users.

Hardware-facing, RF-facing, or field-test work is out of scope for the public repository unless separately reviewed for safety, legality, and export-control compliance.

Overview

robodog-defensive-systems-lab is a defensive research repository for synthetic simulation, resilience testing, secure coordination, and autonomy-safety boundaries.

The repository focuses on:

• synthetic signal-environment modelling;

• communications-degradation resilience testing;

• secure communications for autonomous systems;

• formation-safety checks;

• safe-state behaviour;

• non-operational anomaly detection;

• formal/interface safety boundaries.

Applications include civil resilience, search-and-rescue coordination, disaster-response robotics, secure autonomous-system research, and defensive safety analysis in lawful, authorised environments.

ECM-related terminology in this repository is used in the limited sense of defensive spectrum-awareness, interference modelling, resilience, classification, and safety simulation. It is not used to describe operational interference, offensive activity, or field deployment guidance.

What This Repository Is

This repository is a defensive research platform for autonomous-system resilience. It focuses on synthetic signal-environment modelling, secure communications, formation-safety checks, and safe-state behaviour for coordinated robotic systems.

ECM-related work is limited to non-operational simulation, detection, classification, resilience testing, and safety documentation.

What This Repository Is Not

This repository is not a weapons project, surveillance project, operational ECM toolkit, RF attack toolkit, or deployment guide.

It does not provide instructions for unlawful interference, real-world jamming, target tracking, evasion, intrusion, or offensive autonomous behaviour. Any examples are synthetic, constrained, and intended for safety analysis, resilience testing, and formally bounded research.

Relationship to Other Projects

This repository is separate from:

• anvomidav - figure-skating choreography and civilian motion modelling;

• robot-vacuum-cleaner - domestic robot simulation.

It is related to broader research on:

• safe formation geometry and separation checks;

• secure communication protocols for coordinated systems;

• autonomy safe-state behaviour under degraded communication;

• interface contracts and ABI safety boundaries.

Architecture

The repository is organised around a simulation-first safety boundary:

Area	Role
Rust core	Synthetic signal-environment models, communications-degradation classification, formation checks, and safe-state logic.
Ada/SPARK safety layer	Formal specifications for safety-critical limits, separation constraints, communication-loss behaviour, and safe-state transitions.
Idris2 ABI layer	Dependent-type interface contracts for data shapes, safety boundaries, and cross-language calling conventions.
Zig FFI layer	C-ABI bridge for bounded interface experiments and type-mirror checks.
Trust and compliance files	Publication-safety, export-control, provenance, and repository-policy documentation.

See TOPOLOGY.md for the architecture map and completion dashboard.

Technology Stack

Layer	Language	Purpose
Core	Rust	Synthetic spectrum-awareness modelling, secure coordination experiments, formation-safety checks, and safe-state behaviour
Safety	Ada/SPARK	Formally specified safety-critical subsystems
ABI	Idris2	Dependent-type interface contracts and safety-boundary proofs
FFI	Zig	C-ABI bridge between ABI definitions and implementation experiments
API	Zig	Consumer-facing interface surface for bounded research workflows

• Cryptography: ML-KEM, ML-DSA, and SLH-DSA, the NIST-standardised post-quantum cryptographic families derived from the Kyber, Dilithium, and SPHINCS+ submissions.

• Spectrum-awareness modelling: synthetic signal-environment data only; no real RF captures.

• Coordination: formation geometry, separation checks, communication-loss handling, and safe-state behaviour.

Implementation completeness should be evaluated from the code and tests, not inferred from roadmap terminology.

Current Status

Phase: v0.1 Foundation

Completion: approximately 40%

Implemented or partially implemented:

• synthetic signal analysis and interference classification;

• post-quantum cryptographic protocol experiments;

• formation geometry and separation checks;

• safe-state and communications-loss behaviour;

• export-control and publication-safety documentation;

• SPARK safety specifications for spectrum-awareness, formation, and autonomy boundaries;

• Idris2 ABI definitions for typed interfaces;

• Zig FFI bridge experiments for classification, distance, and formation checks;

• Trustfile-based repository checks for provenance, safety boundaries, and compliance metadata.

Compliance and Export-Control Notice

This repository may contain dual-use research artifacts involving cryptography, autonomous-system coordination, spectrum-awareness modelling, and safety analysis. It is published as non-operational research and is subject to the safety and publication boundary above.

Users and contributors are responsible for complying with all applicable laws, sanctions regimes, institutional policies, and export-control requirements. Nothing in this repository is legal advice or an authorisation to perform restricted activity.

See EXPORT-CONTROL.md for the compliance notice and DEFENSIVE-USE.md for repository use policy.

Roadmap

v0.1 - Foundation

• Export-control and publication-safety documentation

• Synthetic signal-environment modelling

• Cryptographic protocol design

• Formation-safety primitives

• Safe-state and communications-loss behaviour

• Interface and ABI safety boundaries

v0.2 - Core Technologies

• Synthetic signal-environment simulator

• Communications-degradation resilience tests

• Secure communication protocol experiments

• Formation-safety verification

• Non-operational anomaly-detection models

• Export-control and publication-safety review before any hardware-facing work

v0.3 - Integration

• Multi-agent simulation

• Safety-case dashboard

• Secure key-distribution simulation

• Performance benchmarks on synthetic data

• Hardware-in-the-loop planning document only, subject to separate compliance review

License and Use Policy

Code license: MPL-2.0, unless otherwise stated in individual files.

Additional repository policy: see DEFENSIVE-USE.md.

Compliance notice: see EXPORT-CONTROL.md.

The defensive-use and export-control notices describe project policy and publication boundaries. They should not be confused with the OSI status of the code license.

Authors

Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>

Acknowledgments

This research is maintained with explicit publication-safety, export-control, and autonomy-safety boundaries for defensive and civil-resilience research.