Why a pack, rather than a professional-services engagement
The expensive part of a public-sector deployment is rarely the software. It is the eighteen months spent translating a statute into a data model, a retention rule, a role, an approval step and an audit report, and then defending that translation to an oversight body that has seen it done badly before.
A pack is that translation, shipped: the object and link types, the workflow templates with their approval gates, the retention and dissemination rules, and the control mappings, all deployed in dependency order with per-cell version tracking so a pack can be rolled back, upgraded or run side by side with the previous version.
6 capability packs
Each pack is off until an operator activates it, and each brings its own domain model rather than a renamed generic one.
Law Enforcement
People, incidents, cases, vehicles, and the investigative and operational relationships between them, from bail-out-list matching through pattern-of-life analysis, and from incident intake through case closure.
Regulatory bindings encoded in the pack
- CJIS Security Policy
- 28 CFR Part 23 (criminal intelligence systems)
- IACP model policies
- NCIC operating rules
- DOJ BJA standards
- Pluggable per-state open-records variants
Corrections
Inmates, juvenile residents and immigration detainees; custody and supervisory relationships; and security-threat-group intelligence, across a population whose legal treatment differs by category.
Regulatory bindings encoded in the pack
- PREA (28 CFR Part 115)
- ACA adult and juvenile standards
- ICE detention standards
- JJDPA sight-and-sound separation
- CJIS
- 28 CFR Part 23
- HIPAA plus state corrections-medical rules
Intelligence Community
The full intelligence lifecycle (requirements, collection management, all-source production, dissemination and feedback) with dissemination controls, source-and-method protection, compartments, originator control, foreign-disclosure caveats, request-for-information queues, finished-product lifecycle and tearline production. 24 object types, 22 link types, 16 skills, 14 workflow templates and 13 real-time signal templates.
Regulatory bindings encoded in the pack
- ICD 503, 705, 710, 501, 304, 203, 204
- CNSSI 1253
- EO 12333
- EO 13526
- PPD-28 (US-person minimisation)
- Attorney General investigative guidelines
- Title 10 / Title 50 / FISA handling
Fusion Centers
Suspicious-activity reporting, deconfliction across participating agencies, information-sharing-environment workflows, and the privacy and civil-liberties protections that govern all of it.
Regulatory bindings encoded in the pack
- 28 CFR Part 23
- DHS Fusion Center Baseline Capabilities
- ISE Functional Standard for SARs
- ISE privacy / civil-rights / civil-liberties protections
- Regional deconfliction
- Watchlist handling
- Community-trust standards
Campus Safety
Behavioural threat assessment, emergency notification and incident handling across a mixed minor and adult population, the case where two records of the same kind are governed by different statutes depending on who they describe.
Regulatory bindings encoded in the pack
- Clery Act
- Title IX
- FERPA (directory versus education record)
- HIPAA for campus clinics
- IDEA and Section 504
- COPPA
- Drug-Free Schools
- VAWA on-campus
- Hate-crime statistics reporting
- Threat-assessment and emergency-operations-plan models
Emergency Management
Incident command, preparedness, response and recovery workflows, public alerting and mutual aid, including the reporting shape that federal reimbursement depends on.
Regulatory bindings encoded in the pack
- HSPD-5 · HSPD-8 · PPD-8
- NIMS
- National Response Framework and annexes
- Incident Command System
- HSEEP
- CPG-101 and CPG-201 (THIRA)
- IPAWS
- Stafford Act / 44 CFR
- EMAC
What a pack is, and what it is not
A pack encodes a control mapping. That is not the same as holding an authorisation to operate, and we will not present it as one: these packs are not certified, not accredited and not authorised, and no System9 component has completed our own acceptance programme. What the pack does is shorten the distance between a requirement and the evidence that answers it, because the evidence is assembled from an audit chain the platform is already writing.
Where a control needs proof rather than a mapping, the underlying mechanisms are the ones described across the security platform , tamper-evident chains with counted gaps, classification enforced inside the engine, and refusals recorded at the boundary rather than logged after the fact.