Warrant lifecycle
Support configured draft/submitted review, approval, denial, return for revision, activation, service, recall and other warrant states with history.
Arrest is not conviction. The system should know the difference.
AXIOS keeps warrant review, allegations, charging state, disposition, conviction, sentencing and resulting legal state as distinct, attributable concepts so downstream records do not have to guess what happened.
Legal workflow integrity
Preserve the difference between what was alleged and what was decided.
Charging & case state
Keep arrest records separate from charging and court-review state instead of treating every arrest as a court outcome.
Disposition
Record conviction, dismissal, acquittal, amendment or other configured outcomes separately from the original allegation.
Signatures & review
Workflow engines can preserve reviewer remarks, approvals, signatures, returns, resubmission and audit attribution.
Derived legal status
Felony and other legal consequences can be derived from qualifying authoritative outcomes rather than a permanent manual checkbox.
Connected records
Later officer inquiry can show the legal provenance behind a status while preserving the original record history.
Reusable review architecture
Judicial review can use the same accountable workflow principles as operational approvals.
Submitted legal records can move through configured review stages with return-for-revision, remarks, signatures, timestamps and resubmission history instead of relying on silent status changes.
Authoritative outcomes
When a legal outcome becomes authoritative, downstream state such as qualifying felony status or other configured consequences can reflect the outcome rather than the initial arrest alone.
Module-aware fallback
Judicial capability can deepen the workflow when enabled, but originating law-enforcement records should remain resolvable when the downstream module is not part of the community's configuration.