Casework analytics, in jurisdiction.
Raw records that must stay in their jurisdiction stay there; the agent runs in-jurisdiction and computes beside them. A residency review reads locality, lineage and access logs off the run itself.
The casework cycle, district by district.
The case file stays in its jurisdiction from intake to report. So does the analytics that reads it.
Intake
A case enters through a district office or a portal and lands in the system of record.
records stay in-jurisdiction
Assignment
Cases route to officers. Backlogs start forming here.
Processing
Documents, checks and decisions accumulate on the case file.
Decision
The outcome is recorded. The file closes or escalates.
Reporting
Throughput by district, backlog age, and where the queue actually stalls.
K·03 computes beside the case store
locality, lineage and access logs are properties of the run · the shape a residency review asks for
Throughput, backlogs, and who read the file.
Live views over the case store as it stands, read in-jurisdiction.
K·03 · live views
Ranked backlog attention with reasons, so intervention starts in the right district.
K·03 · attention queue
One row per read on the in-boundary ledger: question, rule, reader, timestamp.
K·02 · audit
Where the agent sits.
KEZEL · DEPLOYMENT · PUBLIC SECTOR
- agent
- deployed in-jurisdiction
- components
- K·02 orchestration + K·03 analytics
- residency
- raw records stay in-jurisdiction
- audit
- in-boundary ledger
Designed to support residency obligations through locality, lineage and access logs rather than paperwork after the fact.
Show us the data you are not allowed to move.
That's the workload we should discuss. Start with a demo on our sample boundary; move to a pilot in yours once your security review clears it.