AI products · Local prototype · partial integration
Relief Atlas
Everyday help, with clear responsibility.
A local coordination prototype for meals, friendly visits and rides among invited family and friends, with reviewable plans and explicit responsibility states.
Recorded prototype
Recorded local prototype · fictional records
The question
Sending a request is not the same as someone accepting it or completing the help. A coordination system should make those differences visible.
How it works
- Draft a small plan from an organizer request, require explicit deadlines and eligible helpers, then review exact recipients and messages.
- Keep location private until acceptance; separate queued outreach, accepted responsibility, reported completion and organizer confirmation.
- Provide review-only MCP drafting, saved drafts, hypothetical decline rehearsal and a local failure lab.
Evidence & results
- Retained local HTTP/MCP and API checks cover review boundaries, idempotency and fictional organizer/helper journeys.
- A captured local UI demonstration shows one confirmed task, uncovered work and an unapproved recovery plan.
- Infrastructure templates and scoped PostgreSQL fault records exist; they are not cloud deployment evidence.
Scope & next steps
- Fictional data and simulated outreach; no measured beneficiary impact or completed human study.
- No live AWS, Alexa+ or email delivery is demonstrated by the demo.
- Later component additions are not a completed integrated release.
Go one level deeper.
Ask about the implementation, tradeoffs, or my contribution.
Explore with the portfolio guide