Decision owner
Caseworker with participant
The named role remains accountable for the consequential decision.
Nonprofit & Social Impact
Designed for Caseworker
Help the caseworker move a participant through a multi-program service plan by grounding eligibility, benefit interactions and referral options in current program rules and the participant's own consented record, so scarce caseworker time goes to the relationship rather than to rule lookup.
Contract NON-01 · primary aggregate ParticipantServiceCase · mode loading
Decision brief
This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.
The evidence and control points that shape this recommendation.
Decision owner
Caseworker with participant
The named role remains accountable for the consequential decision.
Governed evidence
6 record types
Structured records and cited text ground the recommendation.
Workflow
5 controlled stages
Each transition records its input, output, status, and audit context.
Human controls
3 approval gates
Approval gates prevent the copilot from making consequential decisions.
A caseworker supports a single parent enrolled in a workforce program who is offered a wage increase through a placement.
Help the caseworker move a participant through a multi-program service plan by grounding eligibility, benefit interactions and referral options in current program rules and the participant's own consented record, so scarce caseworker time goes to the relationship rather than to rule lookup.
ReferralRecord gives Caseworker the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Step 1 of 5
| Field | Value |
|---|
| Field | Value |
|---|
The output appears here immediately. More technical evidence remains available below.
The demonstration keeps deterministic controls, AI assistance, and approval separate.
Source systems enforce identity, workflow order, policy filters, and record updates.
Retrieval and generation assemble relevant evidence into a cited recommendation or draft.
Caseworker with participant verifies material claims and approves the consequential action.
Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.
Human approval required
What happens: Caseworker with participant performs strengths and needs intake with consent using participantConversation and produces ParticipantCase. A named human approver must review the evidence before the transition completes.
Why it matters: ParticipantCase gives Caseworker program copilot the evidence needed to begin Program rule and eligibility grounding, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/strengths-and-needs-intake-with-consent
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Caseworker program copilot performs program rule and eligibility grounding using ParticipantCase and produces ProgramRuleChunk. The transition is deterministic and does not require autonomous model approval.
Why it matters: ProgramRuleChunk gives Caseworker program copilot the evidence needed to begin Benefit interaction analysis, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/program-rule-and-eligibility-grounding
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Caseworker program copilot performs benefit interaction analysis using ProgramRuleChunk and produces BenefitInteractionFinding. The transition is deterministic and does not require autonomous model approval.
Why it matters: BenefitInteractionFinding gives Caseworker with participant the evidence needed to begin Service plan co-creation, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/benefit-interaction-analysis
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Human approval required
What happens: Caseworker with participant performs service plan co-creation using BenefitInteractionFinding and produces ServicePlanGoal. A named human approver must review the evidence before the transition completes.
Why it matters: ServicePlanGoal gives Caseworker the evidence needed to begin Referral with consent and capacity check, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/service-plan-co-creation
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Human approval required
What happens: Caseworker performs referral with consent and capacity check using ServicePlanGoal and produces ReferralRecord. A named human approver must review the evidence before the transition completes.
Why it matters: ReferralRecord gives Caseworker the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/referral-with-consent-and-capacity-check
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Run a stage to see its explanation, evidence, full request, and full response.
Ask a question and receive an answer grounded in retrieved ParticipantServiceCase evidence.
Select a starter question or enter your own.
Loaded live from /api/config, /api/domain/model, and
/api/domain/sample.
participantServiceCases/tenantId + /caseIdA caseworker supports a single parent enrolled in a workforce program who is offered a wage increase through a placement. The copilot cites the funder rule and the state income threshold showing the increase would reduce childcare subsidy by an amount exceeding the wage gain in the first six months, then identifies a transitional childcare provision that preserves the subsidy for 90 days if applied for before the wage change takes effect. It raises a benefit interaction finding, the caseworker discusses the timing with the participant, they agree on a goal sequencing the application ahead of the placement, and a referral is made with consent basis and current provider capacity recorded.
| Container | Role | Hierarchical partition key | Document types |
|---|---|---|---|
participantServiceCases |
Primary | /tenantId + /caseId |
ParticipantCase, ServicePlanGoal, ReferralRecord, EncounterNote, BenefitInteractionFinding |
programRuleLibrary |
Reference | /tenantId + /programCode |
ProgramRuleChunk |
| Type | Container | Partition key | Identifier pattern | Embedding fields |
|---|---|---|---|---|
ParticipantCase |
participantServiceCases |
/tenantId + /caseId |
case::{caseId} |
None |
ProgramRuleChunk |
programRuleLibrary |
/tenantId + /programCode |
program::{programCode}::rule::{ruleDocId}::{chunkOrdinal} |
chunkVector |
ServicePlanGoal |
participantServiceCases |
/tenantId + /caseId |
case::{caseId}::goal::{goalId} |
None |
ReferralRecord |
participantServiceCases |
/tenantId + /caseId |
case::{caseId}::referral::{referralId} |
None |
EncounterNote |
participantServiceCases |
/tenantId + /caseId |
case::{caseId}::encounter::{encounterAtUtc}::{encounterId} |
None |
BenefitInteractionFinding |
participantServiceCases |
/tenantId + /caseId |
case::{caseId}::interaction::{findingId} |
None |
Order the caseworker's caseload by the goals and referrals with the nearest due dates. Application-side partition-key fan-out caseworker worklist: bounded by the tenantId prefix, the responsible caseworker and a due-date horizon.
participantServiceCases
partition-key-fan-out
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.type = 'ServicePlanGoal' AND c.responsibleParty = @caseworkerUpn AND c.progressState IN ('notStarted','inProgress') AND c.targetDateUtc <= @horizonUtc ORDER BY c.targetDateUtc ASC
Retrieve only the program and funder rules in force for the participant's enrollment date.
programRuleLibrary
partition-key-fan-out
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.programCode IN (@candidateProgramCodes) AND c.type = 'ProgramRuleChunk' AND c.effectiveFromUtc <= @enrollmentDateUtc AND c.effectiveToUtc >= @enrollmentDateUtc ORDER BY RANK RRF(VectorDistance(c.chunkVector, @queryVector), FullTextScore(c.chunkText, @queryTerms))
Surface unresolved findings where one enrollment would harm another benefit.
participantServiceCases
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.caseId = @caseId AND c.type = 'BenefitInteractionFinding' AND c.reviewState = 'open' ORDER BY c.raisedAtUtc ASC
Review which partner referrals actually closed successfully to inform the next handoff.
participantServiceCases
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.caseId = @caseId AND c.type = 'ReferralRecord' AND c.referredAtUtc >= @programYearStartUtc ORDER BY c.referredAtUtc DESC