Public Sector packs
The Public Sector packs are the government-facing family of industry packs: activatable bundles that stand a public-sector mission up on the governed substrate in one deployment. Each pack is starter content built to be extended, its ontology, skills, authorization and compliance policies, workflows and dashboards register into the governed catalog and inherit the cell's identity, classification and audit model, so a public-sector deployment does not run a parallel security plane of its own.
The reachable slice
The pack family and its deployment engine are wired: the six packs are activatable through the Public Sector marketplace tab, and activating one runs the same deployment engine every pack uses, registering ontology, skills, authorization and compliance policies, workflows and dashboards into the catalog, idempotently and with best-effort rollback. That deployment path is the reachable, available capability.
The six packs
| Pack | Mission it seeds |
|---|---|
| Law Enforcement | Case, incident and records ontology, skills and dashboards for a law-enforcement agency |
| Corrections | Custody, facility and case management starter content |
| Intelligence Community | Intelligence-analysis ontology and workflows under the platform's classification model |
| Fusion | Multi-source fusion-center content: cross-agency object and link types with the governance to hold them apart |
| Campus | Campus safety and operations starter content |
| Emergency Management | Incident, resource and response ontology and workflows for emergency management |
Activation and deployment
*Figure: a Public Sector pack is chosen and activated in the Public Sector marketplace tab (cyan, in-flight), then the deployment engine registers its ontology, skills, policies, workflows and dashboards into the catalog (green), where the cell's classification, deny-closed policy and audit govern them.
Table equivalent
| Step / part | State | Reachable? | Note |
|---|---|---|---|
| Choose a pack in the Public Sector tab | in-flight | Yes | The marketplace surface |
| Activate | in-flight | Yes | Runs the shared deployment engine |
| Ontology → managers | deployed | Yes | Origin-tagged, idempotent |
| Skills → catalog | deployed | Yes | The pack's actions |
| Authorization policies + compliance profiles | deployed | Yes | Profiles are declarative, not certifications |
| Workflows + signals | deployed | Yes | Orchestration templates |
| Dashboards | deployed | Yes | Starter views |
| Governed by classification + deny + audit | verified | Yes | Inherited from the cell |
| Declared connectors | registered | Not ingesting | Registration is not an ingest path |
Compliance framing: what a pack does and does not claim
A Public Sector pack ships compliance profiles as part of its bundle. What that means, precisely:
- It does give a deployment a declarative starting point, the object types, policies and controls a mission typically needs, expressed as governed content the platform enforces through its ordinary deny-closed governance and classification ladder.
- It does not certify, accredit, or authorize-to-operate anything. Accreditation is granted by your authority, not by a vendor. A compliance profile is content you extend, and the platform's job is to produce the evidence that accreditation requires.
That distinction is the whole point: the pack accelerates a compliant build; it does not stand in for the accreditation.
Across the deployment matrix
A Public Sector pack is data plus a local deployment step, so it activates on a single cell with no coordinator to reach, the sovereign, air-gapped corner a public-sector deployment usually lives in. Deployed content is ordinary governed catalog content and scopes and replicates like any other across a multi-cell estate. As with every pack, what does not travel is a working data feed: the pack declares its connectors; the ingest path is separate and not asserted by activation.
Related topics
- Industry packs, the pack concept, the deployment engine, and the full catalog.
- Classification ladder, the sensitivity model a Public Sector deployment runs under.
- Governance (deny-closed), the enforcement plane a pack's policies fit into.
- Audit and tamper-evidence the record every deployment and access lands on.