This page is no longer a generic placeholder. It explains how volunteer, events, adopt, and business modules connect to each other and why the pilot runs review-first, backed by live data.
00
Volunteer applications
Review-first pilot
00
Event flows
Calendar and campaign linked
00
Adoption profiles
Moderated handoff
00
Approved businesses
Badged public layer
Pilot principle
Not self-service, but controlled progression: application first, review second, assignment or handoff third.
Exact locations, field access, and institutional touchpoints only open through scoped capabilities.
The public layer stays warm and story-led while the operations layer becomes role-aware.
A member applies with skills, availability, and motivation. The review board applies a rhythm and safety filter before converting anything into an assignment.
Events appear on the public calendar, but draft creation and status changes flow only through elevated-role surfaces.
Public users see temperament and care context; instead of exact location, a controlled handoff note opens only to the authorized chain.
Businesses apply, move through the review chain, and only then open into the badged public listing.
Shared backbone
Volunteer
Creates the human rhythm for field and event work.
Events
Generates visibility for stories and adoption.
Adopt
Carries the most sensitive output of the registry and shelter relationship.
Businesses
Turns neighborhood solidarity into daily physical support points.