Industry Packs
An industry pack is a declarative bundle that stands a vertical up on the System9 substrate in one deployment: its ontology (object and link types), its skills, its authorization and compliance policies, its workflows and reactive signals, its dashboards, and the connectors it expects to draw from. Deploying a pack registers that content into the governed catalog so it inherits the same identity, classification and tamper-evident record as everything else on the cell. A pack is starter content built to be extended, not a finished, certified vertical application.
This area also documents the industrial sensor modalities the platform can take in (radar, sonar and the rest) because a vertical is only as governed as the observations feeding it.
This area is claim-integrity sensitive and overlaps the Intelligence dark verticals. Two rules hold on every page:
- The pack deployment path is reachable; a declared connector is not. A pack deploys its ontology, skills, policies, workflows and dashboards into the catalog, that path is wired. But the connectors a pack declares are only registered: a connector can report healthy with no ingest path behind it, so an activated pack does not imply data is flowing.
- "Public Sector" on every surface. This family is rendered as Public Sector everywhere: heading, label, URL and table. The older US government- market abbreviation for it is internal jargon and is not used in this documentation.
Nothing here is graded, certified, or deployed by virtue of being documented, and no per-pack reachability figure is published by the product registry, none should be inferred.
What's covered
| Page | The reachable slice | Where it stops |
|---|---|---|
| Industry packs | What a pack bundles, how the deployment engine registers it into the catalog (idempotent, with best-effort rollback), and the pack catalog | A pack's declared connectors are registered, not ingesting; the read-only "starter kit" tier suggests an ontology but enforces nothing |
| Public Sector packs | The six-pack Public Sector family: Law Enforcement, Corrections, Intelligence Community, Fusion, Campus, Emergency Management: activatable through the Public Sector marketplace tab | Packs are starter content, not certifications; a bundled compliance profile is declarative, not an attestation |
| Industrial & sensor support | Radar ingest and the on-device signed-capture provenance tier feeding the decode → extract → classify → route funnel | Radar is available today; sonar, laser (the nearest thing to lidar), thermal, seismic and acoustic modalities are on the roadmap |
The pack families
System9 carries more than one thing called a "pack," and they are not the same capability. The split:
- Deployable solution packs (reachable). Two wired families take a declarative bundle and register it into the catalog: the Public Sector solution packs (six packs), and a commercial industry-solutions catalog spanning sixteen verticals (healthcare, insurance, finance, manufacturing, retail, energy, logistics, telecom, agriculture, government, education, media, real estate, oil & gas, cyber insurance, legal).
- Read-only starter kits (suggestion tier). A lighter tier ships a vertical's suggested ontology and extraction/fusion defaults to an observer. These are read-only suggestions, they enforce nothing and deploy nothing. The fusion-stream variant of this tier ships healthcare only today.
The Industry packs page describes the deployable family; the suggestion tier is named there so the two are never conflated.
How it fits the rest of the platform
- A pack's ontology and skills become governed catalog content the moment they deploy, catalogued, classified, and subject to the same governed reads as any other data.
- A pack's authorization and compliance policies fit the same deny-closed governance as every other gate.
- The sensor modalities feed the Sensor Intake funnel, land as governed data, and record every step (including every refusal) on the tamper-evident record.