Government & Public Sector

Citizen Services Navigator

Designed for Citizen

Help a resident understand which public benefit or licensing programs they qualify for, what evidence each program requires, and where their submitted application currently stands, using only published program rules and the resident's own case record.

Contract GOV-01 · primary aggregate ResidentServiceCase · mode loading

Decision brief

Evidence collection and verification: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Resident and intake clerk

The named role remains accountable for the consequential decision.

Governed evidence

5 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

2 approval gates

Approval gates prevent the copilot from making consequential decisions.

Business problem

A resident who lost part-time hours asks what help is available for rent and utilities.

Decision to make

Help a resident understand which public benefit or licensing programs they qualify for, what evidence each program requires, and where their submitted application currently stands, using only published program rules and the resident's own case record.

Outcome to show

determinationNotice gives Eligibility caseworker the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Plain-language needs intake
  2. 2Program rule retrieval
  3. 3Advisory eligibility screening
  4. 4Evidence collection and verification
  5. 5Caseworker determination and notice

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Resident and intake clerk verifies material claims and approves the consequential action.

Workflow stages

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.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved ResidentServiceCase evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Help a resident understand which public benefit or licensing programs they qualify for, what evidence each program requires, and where their submitted application currently stands, using only published program rules and the resident's own case record.
Primary aggregate
ResidentServiceCase
Primary container
residentServiceCases
Hierarchical key
/tenantId + /caseId
Schema version
1

Sample scenario

A resident who lost part-time hours asks what help is available for rent and utilities. The navigator screens three programs, reports likely eligibility for the emergency rental assistance program and the utility hardship credit, and cites the administrative code sections that set the 60 percent area-median-income threshold and the 30-day arrears requirement. It flags that proof of arrears and the most recent two pay stubs are missing. The resident uploads both; verification clears the checklist, and a caseworker issues a determination that references the same cited clauses in the notice sent to the resident.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
residentServiceCases Primary /tenantId + /caseId ServiceCase, EvidenceItem, EligibilityAssessment, CaseNote
benefitPolicyLibrary Reference /tenantId + /programCode EligibilityRuleChunk

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
ServiceCase residentServiceCases /tenantId + /caseId case::{caseId} None
EligibilityRuleChunk benefitPolicyLibrary /tenantId + /programCode program::{programCode}::rule::{ruleDocId}::{chunkOrdinal} chunkVector
EvidenceItem residentServiceCases /tenantId + /caseId case::{caseId}::evidence::{evidenceId} None
EligibilityAssessment residentServiceCases /tenantId + /caseId case::{caseId}::assessment::{assessmentId} rationaleVector
CaseNote residentServiceCases /tenantId + /caseId case::{caseId}::note::{noteTimestampUtc}::{noteId} None

Query patterns