Data Fabric
Sensor to C2, without a programme office. Every sensor, feed and edge node speaks into one fabric, built on sovereign compute.
Ingress
Sensor messaging comes in as SAPIENT (Protobuf/JSON). Additional protocol support is evaluated per engagement. The Stone Soup tracker core, released as open source through Context Foundry, sits at the ingress layer.
Streaming and storage
Data moves through a streaming layer and lands in sovereign object storage. Multiple teams can store, retrieve and query at once without contending for the same pipeline.
Egress
Data leaves the fabric as CoT/ATAK for situational awareness tools and as SAPIENT HLDMM for high level data model consumers, validated against live C2, CRC and CAOC environments.
The connector library
A connector is the piece of code that translates a specific sensor or system's native format into the fabric's ingress format. New connectors are commissioned as new sensors and systems are onboarded. Connector code is available through Context Foundry under Apache 2.0.
Onboarding a new sensor
A new sensor is onboarded by mapping its native output to SAPIENT, validating that mapping against a live C2 environment, then leaving the connector in the library for reuse. This is the step that historically takes a programme office years. We run it in days.