Integration reviews
API, auth, and connector scope
The docs should show what is public, what is tenant-scoped, and which service owns the authentication boundary.
Documentation
Documentation
Technical, deployment, security, and AI-access guidance for teams evaluating or operating the platform in public-safety environments.
Documentation posture
Keep deployment, procurement, and integration evidence in one operator-facing pack.
Core doc lanes
5 tracks
API endpoints covered
200+
Machine-readable access
CLI + JSON
Governance framing
CJIS-ready
Documentation pack
Answer technical, operational, and oversight questions from the same source set
The strongest documentation is not a marketing appendix. It should tell a procurement team how the platform deploys, tell an integrator how data moves, and tell an operator where the controls sit.
Deployment reviews
Boundary and residency expectations
Infrastructure notes need to make tenancy, storage, and network assumptions clear before a security questionnaire starts.
Operator reviews
Evidence of how work is handled
Screens, exports, and audit behavior should show up beside the guidance so teams are not guessing at workflow fit.
Documentation record
Investigation surfaces, source material, and reviewer context should stay aligned with the written guidance.
Quick Start
CLI bootstrap
Bootstrap a connector or operator sandbox quickly, then move into the deeper reference material as requirements sharpen.
npm install -g @argus/cli
argus init task-force-connector
argus auth login
argus devDocumentation tracks
Choose the document set that matches the decision in front of the team
Start with the lane that answers the immediate question, then move deeper into the supporting technical or oversight material.
Map the authentication boundary, service ownership, and endpoint coverage before integration work starts.
Review connector methods, payload expectations, and partner responsibilities for inbound and outbound data flows.
Inspect control posture, disclosure handling, and review-oriented security evidence.
Operational context
The documentation should mirror the actual objects, statuses, and case context operators see in the platform.
Endpoint map
API Reference
Map the authentication boundary, service ownership, and endpoint coverage before integration work starts.
- Auth and API surfaces
- GraphQL, REST, and WebSocket lanes
View documentation
Partner playbook
Integration Guide
Review connector methods, payload expectations, and partner responsibilities for inbound and outbound data flows.
- Connector methods and payload shapes
- Security requirements and testing gates
View documentation
Runbook
Deployment Guide
Compare cloud, hybrid, and on-prem deployment lanes with the infrastructure assumptions attached to each.
- Cloud, hybrid, and on-prem options
- Infrastructure and boundary expectations
View documentation
Governance dossier
Security Documentation
Inspect control posture, disclosure handling, and review-oriented security evidence.
- Control posture and disclosure flow
- Named frameworks and review expectations
View documentation
Machine-readable docs
AI-Accessible Docs
Use machine-readable manifests and topic endpoints that mirror the actual investigation data model.
- Structured endpoints for assistants
- Topic-level retrieval for RAG and training
View documentation
Need a specific document pack?
The integration and solution teams can walk through the exact deployment, security, or API materials your review requires.