Defense · 6 whitepapers · Defensive posture
Defensive by architecture.
NavTrax runs the same engine on an air-gapped node as on a hiker's phone. Every action with a physical effect sits behind a signed human authorization token with a time-to-live and an audit entry, and the system has no effector interface of any kind. That is a structural fact, not a policy paragraph.
Mesh resilience
Per-message keys, sub-two-second repair, jittered beaconing, and a documented response to jamming and GNSS spoofing.
CommunicationsAir-gapped deployment
One ingest path for both postures. Signed bundles, an SBOM, and zero runtime egress.
AwarenessCommon operating picture
An entity model that stays authoritative at the edge, converging peer-to-peer over mesh.
AwarenessCounter-UAS awareness
Detect, classify, advise. No effector interface exists, and that absence is deliberate.
SustainmentCasualty care & MEDEVAC
On-device triage, then the window, the landing zone and the element with the capability.
SustainmentCompliance posture
Stated plainly, including what we do not yet hold.
We publish the gaps too.
A procurement officer will find out either way. Finding out late is worse for both of us.