Beyond the report
The paperwork nobody else builds for
CJIS-aligned architecture
Deployed on Azure Government with CJIS-conscious network egress – down to self-hosted map tiles so no case coordinate touches a public tile server.
Immutable audit trail
Every view, edit, approval, AI call, and export is logged with actor, timestamp, and session – system-wide and per case. Exports carry a verification hash.
Server-side AI, always
Model calls run through a server-side proxy – API keys and case data never reach the browser. Every AI output is drafted, attributed, and human-approved.
Role-based access
Permissions mirror rank and assignment: supervisor review queues, sergeant-gated editing, and least-privilege defaults for every module.
MFA & session controls
Multi-factor sign-in with CJIS-compliant identity providers, encrypted-session indicators, and automatic timeout on idle.
Encryption everywhere
TLS 1.3 in transit, encryption at rest on Azure SQL, and classification banners on every sensitive screen and export.
Accountability by default
If it happened, it’s in the log
Human actions and AI actions share the same trail. When counsel asks who touched a case and when – the answer is one export away, hash included.
Activity log – INC-2026-04418
Law Enforcement Sensitive
19:02:47 · Jul 17Ofc. A. Belloopened new report wizard19:06:12 · Jul 17Narrative draft generated · model + prompt logged19:11:38 · Jul 17Ofc. A. Belloedited narrative · 14 lines changed07:41:05 · Jul 18Sgt. M. Riveraapproved report · note attached07:42:19 · Jul 18PDF export · verification hash SHA-256 9f41…c2a8
For your review board
The questions procurement asks, answered up front
| Hosting | Azure Government (Static Web Apps + Functions), deployed via audited CI/CD pipeline |
|---|---|
| Data at rest | Azure SQL with encryption at rest; agency data logically isolated per tenant |
| Identity | Azure AD B2C / CJIS-compliant IdP integration, MFA enforced, role-based permissions |
| AI processing | Server-side proxy to Anthropic Claude; no keys or case data in the browser; all calls logged with model and prompt metadata |
| Network egress | Self-hosted map tiles and Azure Maps geocoding for strict CJIS egress environments |
| Certifications | SOC 2 Type II in progress; CJIS security addendum available on request |
Full security whitepaper and architecture review available under NDA.