← Technology portfolio

Acquisition, normalization & provenance

Wayfinder

Active development

Different sources produce different shapes of information. Wayfinder handles sensor data integration at the source boundary: acquiring supported observations, preserving what arrived and normalizing it into evidence that downstream systems can use.

Current foundation

Source data with its history attached.

Wayfinder faces source systems. Its current adapters handle acquisition and source lifecycle, preserve source identity and provenance, and translate heterogeneous observations into known evidence formats. Normalization makes information usable without discarding where it came from.

Current source families include supported mobile position and sensor observations, aviation, maritime, water and environmental observations, and weather alerts, forecasts and radar. Support is defined by the current adapters and their data contracts; it does not extend to every device, feed or product in those families.

Source identity distinguishes who or what supplied an observation. Provenance retains its source history through normalization, so downstream interpretation can refer back to the evidence. Current development also includes source-specific aircraft metadata enrichment, kept separate from position observations.

Development direction

More sources, defined boundaries.

Current integration and normalization continue to be refined. Additional authorized adapters, broader source families and compatible downstream consumers are planned directions.

Each new source needs a defined acquisition path and evidence contract. Universal sensor compatibility and automatic understanding of arbitrary formats are not current capabilities.

Architecture & independence

Wayfinder runs as a separate ingestion component, with its own source and evidence inspection. It can operate without Janus or Argus. In the current Recon composition, Janus builds operational context from the normalized evidence.

Wayfinder gets information in; governed interchange through Charon addresses validated exchange between systems. Transaction journaling, delivery retry, quarantine and transaction replay belong to Charon’s exchange foundation.

How we describe development status