LostPaws

LostPaws is the new application repository for the ShelterPawtners business and its LostPaws initiative. It intentionally began as a clean implementation. No Core or RaveShelter application code or architecture is carried forward.

Current state

MVP implementation was authorized on September 6, 2026. The repository now contains a React and TypeScript application plus a committed Supabase migration applied to shelterpawtners-dev.

The current implementation includes responsive public pages, email authentication, protected multi-role routes, a pet-centric Guardian dashboard with active multi-pet selection, Partner organization/profile management, a public Partner directory, immutable Partner offers, exact-version Guardian claims, and an opaque-code Partner redemption workflow. The working redemption UX is awaiting its required Checkpoint 4 review; verified-savings work has not begun. Google sign-in remains disabled until provider credentials and approved redirect URLs are configured. Nothing has been deployed to the public ShelterPawtners domain.

Planned capabilities

ShelterPawtners connects Care, Savings, and Community to support shelter pet adoption and long-term outcomes. The guardian-first MVP is planned to combine a limited Digital Pet Passport with an authenticated savings marketplace. After login, guardians should be encouraged to set up their pet while retaining the option to browse trustworthy public savings immediately.

Later work will add shelter verification and auditable guardianship transfers, private and adoption-qualified offers, partner redemptions and savings measurement, LostPaws community programs, authorized care contributions, and privacy-conscious insights.

LostPaws connects music festival and electronic music communities to this mission as an independent program. Naming a festival or artist does not establish affiliation.

Development setup

Clone the repository, copy .env.example to .env.local, and supply the development Supabase URL and publishable key. Never commit secret or service-role credentials.

npm install
npm run dev
npm test
npm run build

Development work is limited to shelterpawtners-dev. Production connection, project creation, DNS changes, and deployment require explicit user instruction.

Human QA can use the branch-scoped Vercel Preview described in Hosted shared-development QA. It uses only the shared development Supabase URL and publishable key; production remains untouched.

Architecture

The frontend uses React, TypeScript, and Vite with a small custom CSS design system. Supabase provides PostgreSQL, authentication, storage, RLS, and APIs. Edge Functions will be added only for privileged workflows such as external adoption confirmation and email delivery. See Architecture and Security and privacy.

Documentation

• Documentation authority guide: read order, live-status authority, and historical-document boundaries.
• Live project controller: current blockers, active lanes, and next actions.
• Product vision: mission, ecosystem value, and audiences.
• Product requirements: planned behavior and acceptance expectations.
• Marketplace research and savings strategy: initial provider research, offer classifications, and curation standards.
• User roles: multiple roles and scoped organization permissions.
• Brand design system: visual principles and design workflow.
• Content standards: terminology, writing, and truthful claims.
• Architecture: technical direction and engineering standards.
• Roadmap: MVP slices, later phases, approval gates, and human decisions.
• Decisions: durable architecture/product decisions and open owner gates.
• Security and privacy: data protection and authorization requirements.