Intelligence
Intelligence is the System9 product area for turning observation into decisions. Where the Data Platform governs data at rest and in motion, and the Agent Platform governs reasoning and action, Intelligence governs the path from a raw signal, a document, a sensor, an observation, a radio link, to a decision a person can stand behind.
It is not a separate product bolted onto the platform. It runs on the same cell, the same identity and classification model, and the same tamper-evident record as every other capability, so an observation carries its provenance and its clearance the whole way to the decision.
Intelligence spans a very wide domain, and this area is precise about what is available today versus what is on the roadmap. Each page leads with the capability you can use now and marks the rest as roadmap, so an evaluation can be scoped against what is actually there.
The arc
Every surface in this area is a stage of one path, and the path is the product:
An observation that arrives with its own proof, is understood only where that is lawful and possible, and can be refused at any point, is a governed observation system rather than an ingest pipeline.
Three movements carry it, and from capture to decision walks all three in depth:
- Capture produces evidence, not media. A device ships signed digests rather than pixels. What travels is proof that something happened, exactly when it says, unaltered.
- Understanding runs where it lawfully can. On the device, in the cell, or not at all. Where it runs is a design decision rather than an accident.
- Refusal is part of the product. The platform reports what it may not do and why, and compliance outranks technical capability.
Read that page first if you are trying to see the shape. Read the surfaces below if you are evaluating one capability.
Start here: learning an estate you already have
Most evaluations begin in the same place, with data somebody already owns and nobody fully understands.
| Surface | What you get |
|---|---|
| Discovery & Mapping | Scan a data estate in place, normalise it to one canonical semantic model, and reconcile edge findings into a trunk. Nothing is moved to be understood |
| Scanning external platforms | Connect to Databricks, Snowflake, Fabric, the major clouds and VMware: what each reads, what stays put, and how a credential never crosses a service boundary |
| Content Intelligence | Governed content: cryptographic-reputation ranking, provenance verification, interactions and cross-organization federation over published content |
Operational sensing
Turning live signals from equipment and devices into something a person can act on.
| Surface | What you get |
|---|---|
| Predictive maintenance | Condition indicators, state detection, remaining-useful-life bounds with backtesting, and governed advisories that show their reasoning |
| Sensor Intake | Signed capture bundles, and the decode, extract, classify, route funnel, with provenance and classification stamped at each hop |
| Surveillance | The observed to candidate to canonical identity ladder, behind a human gate, with an evidence provenance chain |
Mission and defense
Deployment-gated surfaces for security operations and defense customers. These sit behind licensing and, in the case of Battlefield Operations, export control.
| Surface | What you get |
|---|---|
| Cyber operations | The engagement core: rules of engagement, N-of-M cryptographic approval, scope management, and an engagement audit. Active discovery and exploitation are simulation and modelling, not live testing |
| Tactical Communications | The governed control plane for a field network: mesh routing, delay-tolerant networking, spectrum deconfliction, a station registry, coalition partners as directory trust edges, plus a software-defined radio subsystem a deployment elects per topology |
| Battlefield Operations | Mission-domain decision support across intelligence, fires, defense, logistics and more. Command-plane compute: it models and scores; it does not touch a weapon |
How it fits the rest of the platform
- Observations become governed data the moment they land, catalogued, classified, and subject to the same governed reads as any other data.
- Decisions are made by governed agents and orchestration, under the same delegation and refusal rules as any other agent work, and every consequential decision passes the executive engine's DECIDE organ: a reflex value gate and a deliberative foresight stage that decide identically at the core and the edge. The afferent sensor-fusion front that would feed live observations into that loop is built and parity-pinned but activates on a sensor and model binding (planned). See Sensor Intake.
- Every step (including every refusal) is recorded on the tamper-evident activity record, and access is bounded by the classification ladder.