The Casework Execution Layer
A governed system that drives social and human-services cases forward between deadlines, surfacing judgment calls to caseworkers instead of paperwork.
Where value leaks today.
A caseworker's day is mostly logistics dressed up as care. Documents arrive late and incomplete, deadlines stack across a hundred open files, and the case management system is a place to record what already happened rather than a thing that moves the case. The people who chose this work to help families instead spend it chasing signatures, re-typing assessments into three forms, and reconstructing where a case stands from scattered notes.
A new case management tool rarely changes this, because the tool is a better filing cabinet, not a better worker. It stores the case more neatly but still waits for a human to do every step of moving it: assembling the packet, checking the eligibility math, flagging the missing form, drafting the determination letter. The backlog is made of exactly that human-carried motion, and a filing cabinet — however modern — does not carry anything.
The leak is the gap between recording a case and advancing it. An agency that buys software still owns all the manual advancement; it has just paid to store the problem better. Kitsune forges an execution layer that takes the routine motion off the caseworker — assembling, checking, drafting, chasing — and reserves the human for the assessments and determinations that genuinely require judgment.
One governed flow — agents act, you approve what matters.
Caseworkers spend their hours on the families and the judgment calls, while the system carries the assembling, checking, and chasing that used to swallow the day.
One operating layer — eight governed jobs.
Each is a governed agent inside the same system, sharing context — not eight tools you stitch together.
Case Assembly Agent
Builds a complete case file from intake the moment a case opens, pulling every relevant prior record and document into one working view so the caseworker starts oriented, not buried.
Document Chase Agent
Identifies missing or expired documents, requests them from the right party, and tracks each outstanding item until it lands — without the caseworker holding the checklist in their head.
Eligibility Rules Agent
Runs the case against current policy and eligibility criteria, showing its working so the determination is explainable. It flags edge cases rather than silently guessing.
Determination Drafting Agent
Writes the determination or assessment with cited reasoning tied to the governing rule, ready for a caseworker to approve, edit, or overturn at the human gate.
Deadline Orchestration Agent
Tracks statutory and program deadlines across the full caseload and sequences the next action on each, so nothing slips because a worker was buried in another file.
Continuity-of-Care Agent
Preserves case context across worker handoffs and absences so a transferred case never restarts from zero. The history travels with the case, not the person.
Notice Generation Agent
Produces compliant outcome letters and notices in plain language with correct appeal rights and deadlines, populated from the approved determination.
Review Scheduling Agent
Sets and tracks periodic reviews and redeterminations so ongoing cases get revisited on time instead of drifting until a problem forces attention.
Autonomy you can trust — because the control is built in.
The system acts on its own and every action stays legible, bounded, and reversible. You don't choose between speed and control; the control is what makes the speed safe.
Legible
See what was done, what was declined, and exactly what's waiting on you — nothing happens in a black box.
Bounded
Agents act only within the rules you set. Anything material or irreversible stops at a human gate.
Reversible
Every action is logged and undoable. A wrong turn is caught and rolled back, not discovered weeks later.
Owned
One operating system you own — not a swarm of rented agents you have to police. Built, run, accountable.
Caseworkers spend their hours on the families and the judgment calls, while the system carries the assembling, checking, and chasing that used to swallow the day.
What you're actually getting.
Is this a product or a build?
A build. Kitsune forges a casework execution layer around your programs, rules, and systems of record, and you own the resulting system rather than licensing a seat in a vendor's case tool.
What stays in my control?
Every determination and assessment passes through a caseworker gate. Agents assemble, check, and draft; the human approves, edits, or overrides, and the reasoning behind each call is recorded.
How is this different from a case management platform?
A platform stores the case and waits for a person to move it. The execution layer moves it — gathering documents, running eligibility, drafting determinations — and reserves the caseworker for judgment, not data entry.
How are eligibility decisions kept explainable?
The eligibility and drafting agents cite the governing rule for every step, so each determination arrives with its working shown. That makes outcomes defensible on appeal and transparent to oversight.
What happens when a caseworker leaves or is out?
The continuity-of-care agent keeps full context attached to the case itself, so a reassignment or absence does not reset progress. The next worker picks up where the last left off.
The same foundry, other domains.
Bring us the bottleneck.
We'll forge the operating layer around your friction — built, owned, and running.