Local Resource Index

Index cited local emergency, transit, and human-service resources with authority, freshness, correction, and takedown controls.

jmagly bdf4371 1.2 KB Updated

File contents

Local Resource Index

Process

  1. Register and gate every source before acquisition.
  2. Select cap, gtfs, or hsds; retain the original payload/hash, publisher, profile/version, per-vertical required fields, selectors, mappings, and validation result.
  3. Never infer absent availability, accessibility, cancellations, contacts, or eligibility. Keep not_provided distinct from none.
  4. Apply domain expiry/freshness and public-scope rules. Expired active alerts, unverified publishers, fabricated contacts, and sensitive client data block.
  5. Provide correction/takedown intake and retain an append-only audit chain.
  6. Record the structured-data mapping and pass the record through the civic publication gate before any local publishing handoff.

Output

A local-resource-index record plus block|warn|record findings.

References

  • schemas/local-resource-index.schema.json
  • docs/research/control-source-matrix.md
  • OASIS CAP 1.2, GTFS, and Open Referral HSDS sources in the research brief

jmagly/aiwg/tree/main/agentic/code/addons/civic-action/skills/local-resource-index commit bdf43718bd

Frequently asked questions

npx skillmds@latest add jmagly/local-resource-index