Government Claims — Implementation Guide
Audience: Government agencies, ministries, county governments, implementation teams. Vertical: Government & Public Sector — benefit claims, compensation claims, community tickets, permit disputes. Status: Configuration-only design; cross-agency governance; no bespoke tables. Substrate: Reuses Jijibora community governance (s165-s166), record federation (s184), scope governance (s142).
1. Claim Types — Government
| Claim Type | CNS URI | Bound To | Typical Evidence Required |
|---|
| Government Benefit Claim | cns://claim/type/government/benefit | truth_node:person | Eligibility proof, identity attestation, agency determination |
| Government Compensation Claim | cns://claim/type/government/compensation | truth_node:person | Loss documentation, ministry determination, cross-agency verification |
| Community Ticket | cns://claim/type/community/ticket | truth_node:person | Triage note, reporter info, incident description |
| Permit Dispute | cns://claim/type/government/permit_dispute | resource:parcel | Application, zoning check, quorum decision, deed reference |
| Land Dispute | cns://claim/type/government/land_dispute | truth_edge (ownership) | Title evidence, survey report, encroachment evidence |
2. Agency Mesh Model
Government claims use an agency mesh rather than a provider family. There are no provider maps — claims route between agencies (ministries, counties, departments) through record federation bindings.
| Agency Type | Role | Federation Boundary | CNS Policy |
|---|
| Ministry | Benefit determination | Ministry → County | cns://claim/type/government/benefit may federate ministry→county |
| County | Local administration | County → Community | cns://claim/type/community/ticket may federate county→community |
| Department | Specialized review | Department → Ministry | cns://claim/type/government/compensation may federate department→ministry |
Cross-agency quorum is required for claims that span agency boundaries. Each agency has its own scope with isolation boundaries.
3. Guard Policies — Government
3.1 Separation of Duties
| Claim Type | Creator May Approve? | Barred Pairs | Notes |
|---|
| Benefit Claim | No | Applicant ↔ Determinator | Applicant cannot approve their own benefit |
| Compensation Claim | No | Claimant ↔ Reviewer | Different agencies where possible |
| Community Ticket | Yes (lenient) | — | Community ticket pattern; creator may approve (lenient SOD) |
| Permit Dispute | No | Applicant ↔ Quorum Member | Different parties |
| Land Dispute | No | Claimant ↔ Surveyor | Independent verification required |
3.2 Quorum Bands
| Amount Range | Risk | Quorum | Approver Roles |
|---|
| Any | Low | Assembly quorum | Community representative + agency officer |
| Any | Mid | Two-person | Agency officer + cross-agency reviewer |
| Any | High | Cross-agency | Ministry + county + external auditor |
3.3 Evidence Requirements
| Claim Type | Required Evidence | Source |
|---|
| Benefit Claim | Eligibility proof, identity attestation, agency determination | Identity plane + agency system |
| Compensation Claim | Loss documentation, ministry determination | Ministry records + evidence upload |
| Community Ticket | Triage note, reporter info, incident description | Intake channel (WhatsApp, USSD, walk-in) |
| Permit Dispute | Application, zoning check, quorum decision | Zoning permit scenario + deed record |
| Land Dispute | Title evidence, survey report, encroachment evidence | Land registry mirror + truth_edge graph |
4. Panel — Government
Government claims have no provider mesh in the seeded values. Panel roles cover insurance lines only. Government and community lines use agency mesh routing instead.
| Role | Capabilities Required | Attestation | Lease TTL | Claim Types |
|---|
| Agency Officer | benefit_determine, compensation_review, ticket_triage | Yes | 8 hours | All |
| Cross-Agency Reviewer | inter_agency_review, audit_verification | Yes | 8 hours | Compensation, high-value |
| Community Representative | ticket_assess, community_governance | Yes | 8 hours | Community ticket |
| External Auditor | financial_audit, compliance_review | Yes | 8 hours | Litigation, high-value |
All roles require: approved affiliation + active status + attestation. Fail-closed.
5. SLA Windows — Government
| Claim Type | Severity | Default Window | Escalation To |
|---|
| Benefit Claim | Standard | 45 days | Ministry |
| Compensation Claim | Standard | 90 days | Cross-agency panel |
| Community Ticket | Standard | 72 hours | Ward office |
| Permit Dispute | Standard | 60 days | Zoning quorum |
| Land Dispute | Standard | 180 days | Land tribunal |
6. Intake Maps — Government
| Map ID | Target | Fields Mapped | Source Channels |
|---|
intake:government:benefit | claim creation | person_id, benefit_type, eligibility_documents, agency_ref | Agency portal, walk-in, USSD |
intake:government:compensation | claim creation | person_id, loss_type, loss_documentation, ministry_ref | Ministry portal, evidence upload |
intake:community:ticket | claim creation | reporter_id, incident_type, description, location, triage_note | WhatsApp, USSD, walk-in desk, API |
7. PoCE Integration Points
| Transition | PoCE Trigger | Evidence Recorded |
|---|
| Benefit application | fn::lifecycle::start_poce_session | applicant, benefit type, eligibility docs |
| Benefit determination | fn::lifecycle::record_poce_step | determinator, decision, conditions |
| Compensation claim | fn::lifecycle::start_poce_session | claimant, loss type, documentation |
| Compensation review | fn::lifecycle::record_poce_step | reviewer, cross-agency verification |
| Community ticket | fn::lifecycle::start_poce_session | reporter, incident, triage note |
| Ticket resolved | fn::lifecycle::record_poce_step | resolver, resolution, ward officer sign-off |
| Permit dispute | fn::lifecycle::start_poce_session | applicant, parcel, zoning check |
| Permit decided | fn::lifecycle::record_poce_step | quorum decision, deed record reference |
8. Worked Example — Government Benefit Claim
- Citizen applies for housing benefit via agency portal or USSD.
- Claim created:
cns://claim/type/government/benefit, bound to truth_node:person, PoCE session started, identity attestation required. - Agency officer assigned via panel eligibility (agency mesh, no provider panel).
- Eligibility reviewed — identity verified, income checked, benefit type confirmed.
- Cross-agency review — for amounts above threshold, county + ministry review (cross-agency quorum).
- Benefit determined — approval or denial recorded with reasoning.
- Claim finalized with PoCE receipt: applicant → officer → cross-agency reviewer → determination chain.
Guard check: Applicant ≠ Determinator (SOD enforced). Cross-agency quorum for high-value claims. No benefit without PoCE proof.
9. What We Do Not Build
- No benefit calculation engine. Unless expressible as declarative lookups + solver-gateway capability.
- No agency replacement. Agencies remain the legal determination authority; Sovereign OS mirrors and audits.
- No synthetic "optimal" benefit amount. Solver down → 502/503 fail closed.
- No fake metrics (e.g., "95% benefit approval rate"). Live data or honest empty states.
10. Deployment
- Deploy strata:
s165_community_governance, s166_community_governance_functions, s142_scope_governance_authority, s184_record_federation, s282_processing_claim - Seed CNS types:
cns://claim/type/government/* - Seed lookups: guard policies, quorum bands, SLA windows, agency mesh, intake maps in NATS KV
- Seed scenario packs: benefit claim, compensation claim, community ticket packs
- Test:
GET /v1/claims/processing/readiness — all probes must pass before LIVE