Know when information can still be trusted.
Evidence fusion and mission-context trust assessment for degraded command and autonomous systems.
VERITY is the evidence fusion and trust-assessment capability within the Resolvix AURM Platform. It consumes evidence from HOLDFAST alongside PNT, sensing, telemetry, custody and autonomy-state signals to determine whether delivered messages and the broader mission context remain trustworthy — and to signal when they do not.
Identify uncertainty. Build mission context. Support decisions.
Identify uncertainty
Detect stale, incomplete, contradictory or context-invalid evidence.
Build mission context
Combine communications evidence with positioning, sensing, telemetry and autonomy state.
Support authorised decisions
Produce confidence outcomes, review signals and bounded recommendation candidates for operators and authorised downstream systems.
VERITY is built to inform, not to decide. Assurance outcomes and review signals go to the operator or system that holds command authority — VERITY provides the evidence picture that makes those decisions trustworthy.
Delivery
Packet delivery is HOLDFAST's job.
HOLDFAST keeps critical messages moving across degraded bearers, relays and mesh networks. VERITY sits above the delivery layer — it evaluates what arrived, not how it got there.
Trust assessment
VERITY assesses whether what arrived is coherent enough to act on.
Review signals and assurance outcomes for delivered messages and the broader mission state — so operators and autonomous systems can act with confidence rather than assumption.
What VERITY evaluates.
These evidence categories are at different maturities. Each is labelled — existing bounded simulation evidence, an existing module pending packaging, inferred scenario-context evidence, a planned runtime capability, or a planned live-adapter input.
Evidence
Command freshness
Temporal validity assessment for commands and command context.
Existing bounded simulation evidence
Evidence
Custody continuity
Reasoning about node custody across partition, delay and rejoin events.
Existing bounded simulation evidence
Evidence
Communications continuity
Link-state and message-continuity evidence from HOLDFAST.
Existing bounded simulation evidence
Evidence
Network-state confidence
Route viability, topology and network-state evidence published by HOLDFAST.
Existing bounded simulation evidence
Evidence
PNT confidence
PNT consistency, uncertainty and integrity-indicator evidence.
Planned live-adapter input
Evidence
Sensor and video freshness
Sensing, video and imagery freshness, staleness and frame-confidence evidence.
Planned live-adapter input
Evidence
Telemetry confidence
Bounded confidence in telemetry channel state and content.
Inferred scenario-context evidence
Evidence
Mission-context coherence
Whether commands and state transitions remain coherent under the current mission state.
Existing module, packaging pending
Evidence
Autonomy-state consistency
Whether the autonomy system itself is in a state consistent with the assurance evidence.
Planned runtime capability
Evidence
Audit and provenance
Traceable evidence record for post-event analysis and operator review.
Existing module, packaging pending
Evidence-backed outcomes with full traceability.
VERITY produces specific, traceable assurance outcomes that operators and authorised downstream systems can use for authorised review or action. Each outcome carries a full evidence trace and a review signal where appropriate.
Trusted
Trusted mission state
Degraded
Delivered — review required
Degraded
Delivered — evidence insufficient
Degraded
Delivered — custody state ambiguous
Identified
Delivered — context invalid
Identified
Late or stale command identified
Designed to subscribe to the message layer. Returns an evidence picture.
VERITY is designed to integrate where messages are received and acted on — the inbox of a C2 application, the data bus of an autonomous platform, or the sensor-fusion layer of a C4ISR system.
Integration is designed to run through a future versioned platform-adapter interface — a message-bus subscription (MQTT, DDS or similar) in modern C4I architectures, a lightweight adapter in legacy systems. Adding an adapter, subscription, configuration and downstream policy is a bounded change to the receiving system, not a drop-in.
Candidate integration pattern — not yet implemented or validated
Before VERITY
Incoming message. Act or hold — operator judgement only.
With VERITY
Incoming message + assurance outcome (Trusted / Degraded / Identified) + evidence trace + review signal where appropriate. Operator or autonomous system acts with a structured evidence picture.
VERITY provides the evidence picture. Command authority and packet delivery remain exactly where they belong.
HOLDFAST preserves message continuity and publishes communications evidence. VERITY assesses whether the delivered message, supporting evidence and mission context remain trustworthy.
HOLDFAST, Network State and Sentry produce continuity, network-state and uncertainty evidence under degraded conditions. VERITY consumes that evidence alongside PNT, sensing, telemetry, custody and autonomy-state signals to assess whether a delivered message and the broader mission context remain trustworthy.
Simulation-backed. Hardware validation next.
Current state
Simulation-backed architectural prototype.
Next gate
Phase 1 — standalone modules and a deterministic Node Runtime MVP. Adapter SDK, platform adapters, hardware-in-the-loop and a controlled field pilot follow in later phases.
Not yet claimed
Field validation, RF validation, GNSS anti-spoof validation, anti-jam validation, SDR validation, waveform validation, operational deployment or combat validation.