Skip to main content

Industrial & sensor support

System9 models a broad set of industrial sensor modalities and carries the governed intake path that turns a sensor reading into a typed, classified, provenance-bearing observation. This page is about which of those modalities you can actually reach today. The code models far more than a running cell can reach, so this page is scoped to the reachable slice.

The reachable slice​

Two things are available today:

  • Radar ingest, radar returns brought into the Battlefield Operations track picture. This is the one sensor modality in the reachable set.
  • The signed-capture provenance tier, on the device, a sensor reading is packaged as a signed capture bundle with a tamper-evident hash chain, and each capture is verified against its device certificate before it is persisted. This tier admits on the capture's signature alone and moves no raw sample bytes home. It feeds the Sensor Intake decode → extract → classify → route funnel, which is where a verified capture becomes a governed, classified observation.

The funnel itself is documented in full under Sensor Intake; this page adds the modality view, which sensor types the platform models, and which of them you can actually reach.

The modality picture​

*Figure: the reachable path (green) is radar into the track picture and the signed-capture provenance tier: a signed capture is verified against its device certificate, then flows through decode → extract → classify → route into a governed store.

Table equivalent

Modality / elementStateReachable?Note
RadarmodalityYesThe one reachable modality; feeds the track picture
SonarmodalityNoOn the roadmap
LasermodalityNoNearest thing to lidar; no lidar modality exists; on the roadmap
Thermal / infraredmodalityNoOn the roadmap
SeismicmodalityNoOn the roadmap
AcousticmodalityNoOn the roadmap
Electro-optical / magnetic / multispectralmodalityNoOn the roadmap
Signed capture bundleprovenanceYesTamper-evident hash chain on the device
Verify against device certificateprovenanceYesAdmits on the signature alone; moves no sample bytes
Decode → extract → classify → routefunnelYesDocumented under Sensor Intake
Governed store + recordverifiedYesThe typed observation lands governed
Bulk-sample ingest gateheld apartNoBuilt; nothing calls it in production, so it is not an enforced chokepoint

On the roadmap​

The modality model is broad, and the following are modelled but not yet exposed on a running cell. Radar is the modality available today; scope an evaluation to it and treat the rest as roadmap:

  • Sonar (surface and subsurface), laser (the nearest thing to lidar), thermal / infrared, seismic, acoustic, electro-optical, magnetic and multispectral modalities, all in the defense-operations tree, and on the roadmap.
  • The bulk-sample ingest gate, a fail-closed verify → policy gate → persist decision path with quarantine / reject / throttle / ingest dispositions, is built, but no transport calls it in production, so it governs nothing today.

These exist in the model. Only radar and the signed-capture provenance tier are reachable on a running cell; everything else above is modelled and not yet exposed.

Across the deployment matrix​

The reachable slice is built for the sovereign, air-gapped corner: captures are bundled, hashed and verified on the device, and only governed observations move, so a disconnected sensor still produces verifiable, classified captures with no coordinator to reach. It works single-cell and, where cells can reach each other, multi-cell. The unreachable modalities do not change this picture, because they do not reach intake at all.