Skip to content

[Capability] National benefits registry and continuous program intelligence #5

Description

@chitcommit

Work key

chitty-benefits-national-registry-v1

Decision

Create one canonical capability for national public-benefit and opportunity intelligence. Do not place this inside the existing chittyscrape repository, which is currently TurboTenant-specific.

Mission

Discover, evaluate, ingest, normalize, reconcile, verify, publish, and continuously monitor authoritative benefit-program sources across federal, state, county, municipal, utility, nonprofit, tribal, educational, healthcare, disaster, veteran, housing, tax, and business-incentive domains.

Required layers

  1. Registry of registries — source identity, authority, jurisdiction, access method, trust rank, health, cadence, and ownership.
  2. Program intelligence graph — programs, authorities, jurisdictions, benefits, eligibility rules, evidence requirements, application channels, deadlines, renewals, and supersession.
  3. Autonomous loop — discover → qualify source → ingest → extract → normalize → deduplicate → conflict-check → verify → publish → monitor → revalidate.
  4. Consumer query surface — evidence-backed eligibility matching with uncertainty and human approval gates.

Non-negotiable governance

  • Reuse canonical ChittyOS entity, authority, location, event, document, and provenance models.
  • No new database or schema unless a documented gap analysis proves existing models cannot represent the requirement.
  • Every material field must retain source ID/URL, authority, retrieval timestamp, effective date, jurisdiction, confidence, health state, and next verification date.
  • Conflicting rules are quarantined and escalated; they are never silently resolved.
  • Human approval is required for submissions, outbound communications, or final eligibility determinations.
  • Expose GET /health and GET /api/v1/status; use canonical auth and ChittyTrack observability.

Source health states

live, redirected, stale, unavailable, superseded, conflicting, quarantined.

Pilot jurisdiction

Federal → Florida → Duval County → Jacksonville → FPL, initially focused on adults 65+, homeowners, veterans, disability, utilities, food, healthcare, transportation, housing, tax, and aging-in-place services.

Initial acceptance criteria

  • Seed registry contains authoritative federal sources plus Florida/Duval/Jacksonville/FPL sources.
  • Every published program has a primary source and verification timestamp.
  • Duplicate programs reconcile without losing aliases or provenance.
  • Source-health checks detect HTTP failure, redirects, stale content, changed forms, and supersession.
  • Pilot query can evaluate a 75-year-old homeowner in ZIP 32246 and expose evidence, uncertainty, and missing facts.
  • Compliance triad (CHARTER.md, CHITTY.md, AGENTS.md) is complete and internally consistent.

Implementation queue

  • Ecosystem and duplicate-capability audit
  • Canonical service ownership decision via ChittyRegistry
  • Source taxonomy and trust-scoring contract
  • Existing-model mapping and schema-gap report
  • Federal + Florida pilot seed manifest
  • Discovery and health-check worker
  • Ingestion, normalization, reconciliation, and conflict quarantine
  • Provenance-complete query API
  • Compliance triad and registration payload
  • Tests and deployment readiness audit

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions