humanity.llc Create

Design space · aid

Crisis resource cards

Pocket cards for shelters, food pantries, recovery groups, immigrant aid, and LGBTQ support. Hand them out once - the current resource list can change when phone numbers, hours, or locations shift.

Research, not shipping yet.

Serve without targeting

Ultimate functionality for people in crisis does not mean marketing at them, profiling them, or turning their emergency into your growth story.

The goal is accurate, revocable pointers controlled by the organizations people already trust - not a platform that learns who scanned, when, and where. Humanity is a resolver for signed public status, not a crisis CRM, not legal ID, and not a surveillance funnel dressed as help.

  • Coalition issues the card A local mutual-aid network, clinic coalition, or tenant union signs updates - not humanity.llc “owning” vulnerable users
  • Scanner sees resources, not a dossier No account required to read hotlines and hours · no “verified human” score · no default scan analytics
  • No extracting stories for the product Do not use crisis populations in landing demos, ads, or founder threads as proof the tech “works”

Why stale info is harm

  • Wrong number on a wallet card A closed shelter line at 2 AM is not a neutral mistake - it can burn the last phone credit someone has
  • Live answer, same card Organizer updates network status - scan shows what is true today

Implications easy to miss

Avoiding “we collect name and address” is necessary but not sufficient. Questions worth forcing before any pilot:

Scan trails

  • Who scanned, when, from where - even without login
  • Employer or abuser infers help-seeking from timing
  • Resolver logs become a subpoena target

False authority

  • Card looks “official” because it is printed
  • People trust QR as government or clinic endorsement
  • Stale “verified” copy reads as active when it is not

Coercion & dependency

  • Gate access behind installing an app or account
  • Single operator can kill every card in a city
  • Revoke used to silence, not protect
  • deanonymization via relay
  • language access
  • immigration enforcement risk
  • counter-protest infiltration
  • donor-driven “metrics” pressure
  • volunteer burnout mis-updates
  • photocopied rogue cards
  • mental-health triggering copy

Possibilities not to forget

Live objects open humane options if the coalition stays in charge:

  • Print once, fix in one signed update Clinic moved - every old card shows the new address on next scan
  • Revoke a compromised batch Counterfeit cards in circulation → series revoked → “get a new card at desk”
  • Multilingual status without reprinting Same card, scan language follows browser or coalition publishes parallel lines
  • offline printed fallback number
  • expiring card series
  • separate keys per region
  • plain-language “last updated”
  • no-scan SMS shortcode on card
  • peer org federation
  • minimal scan page (low bandwidth)

What we refuse by design

Not this

  • Crisis people as marketing assets
  • Scan analytics by default
  • KYC to read a hotline list
  • Permanent identity on the card
  • Platform lock-in for coalitions

This

  • Coalition-controlled status
  • Revocable series
  • Honest “what scan does not prove”
  • Inspectable signed updates
  • Exportable, federatable spec

Example · wallet aid card

Scan · current

  • Shelter bed line: open tonight
  • Food pantry: Sat 10–2
  • Crisis line verified · active
  • Updated 3h ago by coalition

Resources moved

  • Clinic relocated - new address
  • Old flyer still in circulation
  • Card scan shows current site

Compromised batch

  • Card series revoked
  • Get updated card at desk

Pilot rule: coalitions run cards with their own keys and copy review - humanity.llc ships the primitive, not the pastoral care.

What the card can show

  • hotlines active
  • hours today
  • walk-in / appointment
  • language offered
  • last updated
  • verified by coalition
  • revoked series

Combining with food freshness tags

A crisis card can point at food help without pretending the whole pantry is one static list. The card shows the trusted resource; each food batch keeps its own freshness state.

Scan · food tonight

  • Community fridge: stocked 5:20 PM
  • Veggie soup batch: expires 10 PM
  • Contains: wheat · no nuts reported
  • Verified by host kitchen

Pantry moved

  • Aid card updates hours and address
  • Individual food tags keep batch-level safety
  • One wallet card, many live resource claims

Recall or outage

  • Recalled batch disappears from safe list
  • Fridge maintenance status shows out of service
  • No scan history needed to protect people

Pair with food freshness tags and proof of maintenance for pantries, fridges, generators, and warming centers.

Functionality without extraction: a card in someone’s pocket stays useful when the answer can change - and when no one had to become the product to get that help.

Save resources (planned)

People should keep important cards - especially crisis ones - without the operator building a scan history.

Use Save this resource / Emergency wallet language, not “collect.” Default: save on the scanner’s device (local folder, optional offline copy) - no account, no “who saved what,” no recent-scans feed on humanity.llc.