Five control surfaces shape how the platform behaves under pressure
Search, model routing, governance, integration, and security are treated as operating controls with review paths, not generic feature checkboxes.
What this section covers
Core platform control surfaces that shape access, routing, and movement through the product.
5
Every feature is expected to follow live access policy and assignment scope.
RBAC-aware
Feature behavior remains tied to connectors, record ownership, and delivery lanes.
Live connectors
Operational actions need visible audit evidence and export paths.
Review-first
Start here if you need to understand how operators move, how data enters and leaves the system, and how policy is enforced once the platform is live.
How to review fit
Treat the feature family like an operating manual, not a marketing grid
Each page focuses on where the control sits, what it governs, and what downstream review teams need to see before deployment.
Review surface
Metrics, queues, graph traversal, and evidence review all live inside the same command-center system rather than separate microsites.
Start with the control you need to evaluate first
Use the cards below as a practical review order for operators, delivery teams, and governance stakeholders.
Connected records
Search, graph traversal, evidence review, and policy checks stay attached to the operating record instead of becoming disconnected feature demos.
Search & Command Surface
Move from operator intent to the right case, entity, evidence item, or command without hopping across disconnected systems.
- Cross-record retrieval without flattening case, entity, or evidence context.
- Role-aware filtering so commands and results stay inside current assignment and policy.
- Direct traversal from search into graph, evidence, and command actions.
Model Routing & Control
Approve which model lanes can touch which work, route by sensitivity and cost, and keep every decision tied to the case.
- Separate public, private, and on-prem model lanes by workload sensitivity.
- Keep routing, approval, and spend decisions reviewable after the fact.
- Prevent ad hoc provider choice from bypassing case and evidence policy.
Security & Compliance
Criminal-justice security controls, audit evidence, and framework mappings for agencies that need their own certification path.
- Focus on deployment posture, access control, and review material instead of blanket claims.
- Map the platform to the frameworks and evidence your own security team will ask for.
- Keep control language grounded in real hosting and operator workflows.
API Integrations
GraphQL, REST, and event delivery lanes for CAD, RMS, evidence, watchlists, and partner systems without flattening the case record.
- Preserve authoritative records while still syncing the parts teams need to act on.
- Choose query, sync, or live event delivery based on the operational job instead of one connector pattern.
- Keep payload shape tied to case, entity, and evidence relationships.
Platform Governance
Access policy, audit evidence, federation boundaries, and review controls that keep investigative tooling accountable under scrutiny.
- Review tenancy, delegated administration, and approval boundaries before rollout.
- Make audit evidence and operator review paths visible to supervisors and compliance teams.
- Keep cross-agency coordination possible without dissolving ownership boundaries.
Review the platform controls against the systems you already run
Walk through search, model routing, governance, and integration fit with the environment you actually have.