| name | access-for-seniors |
| description | Product, engineering, compliance, and GTM assistant for Access For Seniors — a HIPAA-aligned, multi-tenant SaaS platform for senior connection, engagement scoring, caregiver alerts, family outreach, and aging-services navigation (OAA, Medicare, Medicaid, AAA). Part of the "Access To" civic tech initiative. Covers 28 enterprise modules, the conversation engine, memory capture, MCP tool schemas, DynamoDB/RDS data models, AWS CDK deployment, Clerk + Cognito auth, and Stripe billing. Trigger on "Access For Seniors", senior loneliness or isolation work, senior living SaaS, caregiver dashboards, aging-in-place tech, resident engagement, family outreach, OAA programs, AAA referrals, Area Agency on Aging, or any of the 28 modules by name.
|
Access For Seniors — Skill
Purpose: Guide all product, engineering, compliance, and go-to-market work on
Access For Seniors — a multi-tenant SaaS platform that uses AI to detect senior
loneliness, generate meaningful conversations, coordinate family outreach, surface
alerts to caregivers, and connect older adults to aging-services resources.
Initiative context: Access For Seniors is part of the "Access To" civic tech family
(alongside Access To Health, Access To Jobs, Access To Housing, Access To Education,
Access To Safety, Access To Services, Access To Peace, Access To Business). Shared
values: equity, trauma-informed design, community-grounded, evidence-based.
1. System Overview
What Access For Seniors Does
- AI Companion — Natural, memory-aware conversations with seniors via text and voice
- Engagement Signals — Multi-signal detection of reduced social connection (never diagnoses)
- Caregiver Dashboard — Real-time alerts, resident profiles, shift notes, reporting
- Family Outreach — AI-generated, warm messages that encourage family connection
- Aging-Services Navigation — Connect seniors and families to OAA programs, Medicare,
Medicaid, AAA, Meals on Wheels, caregiver support, and elder rights resources
- Multi-Tenant SaaS — Single facilities, multi-site orgs, and health system enterprises
Who It Serves
| Role | Primary Interface | Key Need |
|---|
| Senior / Resident | Voice + Mobile | Natural, low-friction conversation and service connection |
| Family Member | Mobile + Web | Peace of mind, connection reminders, caregiver coordination |
| Caregiver / Staff | Dashboard | Alerts, notes, resident context, resource referrals |
| Facility Admin | Admin Portal | Tenant config, billing, reporting |
| Enterprise Operator | API + Admin | Multi-site management, analytics |
| AAA / Community Worker | Navigator Portal | Resource referral tracking, eligibility screening |
2. Tech Stack (Canonical)
Frontend
- Web: React 18 + Vite + TypeScript
- Auth: Clerk (
@clerk/react)
- Mobile: React Native + Expo (cross-platform)
- Styling: Tailwind CSS
- State: Zustand or React Query
Backend
- API: Node.js + Express (TypeScript) or AWS Lambda functions
- AI/LLM: Anthropic Claude API (conversation engine, message generation, engagement scoring)
- Voice: Twilio Voice + ElevenLabs STT/TTS (or AWS Transcribe + Polly)
- MCP: Custom MCP server exposing Access For Seniors tools to Claude
AWS Infrastructure
- Compute: Lambda (serverless) or ECS Fargate
- Database: DynamoDB (primary), RDS Aurora (reporting/analytics)
- Storage: S3 (audio files, exports, documents)
- Auth: Amazon Cognito (enterprise/SAML tenants) + Clerk (consumer/staff web)
- Messaging: SES (email), SNS (push), Pinpoint (SMS campaigns)
- Secrets: SSM Parameter Store (SecureString) — never hardcode
- IaC: AWS CDK (TypeScript preferred)
Billing
- Stripe: Subscriptions, metered usage, multi-tenant billing
- See
references/billing.md
CI/CD
- GitHub Actions → ECR/Lambda deploy
- See
references/cicd.md
3. Module Map
Access For Seniors has 28 numbered enterprise modules plus named system components.
For detailed specs on any module, read references/modules.md.
Named System Components:
| Component | Reference File | Purpose |
|---|
| Conversation Engine | references/conversation-engine.md | LLM orchestration, turn management |
| Memory Capture | references/memory-capture.md | Persistent resident context |
| Engagement Scoring | references/engagement-scoring.md | Connection signal detection |
| Message Generator | references/message-generator.md | Outreach copy generation |
| Family Outreach | references/family-outreach.md | Family notification workflows |
| Voice Interface | references/voice-interface.md | Voice call + transcription |
| Alerts System | references/alerts-system.md | Risk threshold → alert routing |
| Caregiver Dashboard | references/caregiver-dashboard.md | Staff-facing UI |
| Community Features | references/community-features.md | Group activities, shared spaces |
| Analytics | references/analytics.md | Resident + org-level reporting |
| Notifications | references/notifications.md | Multi-channel delivery |
| MCP Tools | references/mcp-tools.md | MCP schema + tool definitions |
| Aging Services | references/aging-services.md | OAA, Medicare, AAA, resource referral |
Infrastructure Components:
| Component | Reference File | Purpose |
|---|
| Multi-Tenant | references/multi-tenant.md | Tenant isolation, config |
| Auth | references/auth.md | Cognito (enterprise SSO/SAML) + Clerk (staff/consumer) |
| Billing | references/billing.md | Stripe subscriptions + metering |
| AWS Deployment | references/aws-deployment.md | CDK stacks, Lambda, ECS |
| CI/CD | references/cicd.md | GitHub Actions pipeline |
| Security | references/security.md | HIPAA controls, encryption |
| Data Models | references/data-models.md | DynamoDB + RDS schemas |
| Mobile App | references/mobile-app.md | React Native / Expo |
4. Core Workflows
Feature Design Request
- Identify the module(s) involved → read the relevant reference file(s)
- Clarify which user role is affected
- Output: Goals, Non-goals, User stories, Data model changes, API routes, Security notes, Edge cases, Test plan, Rollout plan
- Flag HIPAA/privacy implications if resident data is touched
Data Model / API Request
- Read
references/data-models.md for existing schemas
- Propose additions using DynamoDB single-table design (PK/SK/GSI pattern) or RDS schema
- Include TypeScript types for all new entities
- Security: confirm tenant isolation on every new access pattern
Engagement Scoring / AI Request
- Read
references/engagement-scoring.md
- Treat resident data as PHI — apply minimum necessary principle
- Score outputs are signals, not diagnoses — always frame clinically conservatively
- Never present AI-generated engagement scores as clinical or medical assessments
Aging-Services Navigation Request
- Read
references/aging-services.md
- Match need to program (OAA Title III-B, III-C, III-D, III-E, VII; Medicare Parts A–D; Medicaid LTSS; AAA; Meals on Wheels; etc.)
- Provide eligibility criteria, how to apply, and referral handoff
- Cite primary sources (acl.gov, medicare.gov, cms.gov, state AAA)
Infrastructure / Deployment Request
- Read
references/aws-deployment.md + references/cicd.md
- Default to CDK TypeScript, least-privilege IAM, SSM SecureString for secrets
- Never output hardcoded credentials or ARNs as literals
Marketing / GTM Request
- Read
references/gtm.md for positioning, ICP, messaging
- Maintain brand voice: calm, professional, empathetic, practical
- Never use fear-based messaging about loneliness or aging
- Align with "Access To" initiative values: equity, trauma-informed, community-grounded
5. Security & Compliance Defaults
NOTE: Access For Seniors handles senior health/behavioral data that may constitute PHI
under HIPAA. Apply HIPAA-aligned defaults unless tenant explicitly opts out.
- Encryption: All data encrypted at rest (DynamoDB/RDS KMS) and in transit (TLS 1.2+)
- Tenant Isolation: Every DynamoDB query includes
tenantId condition; RDS uses row-level security
- Audit Logging: CloudTrail + application-level audit log for all PHI access
- Secrets: SSM SecureString or Secrets Manager — never
.env committed to repo
- Auth: Cognito for enterprise (SAML/OIDC); Clerk for staff web; JWT validation on every Lambda
- Data Retention: Configurable per tenant; default 7-year retention for care records
- Consent: Resident/family consent captured and stored before AI interaction begins
- AI Outputs: Never present engagement scores as clinical diagnoses; always frame as "connection signals"
- BAA: Require BAA with AWS, Stripe, Anthropic, Twilio, ElevenLabs, Clerk, and any other sub-processor handling PHI
- Elder abuse mandatory reporting: Where applicable (state-dependent), system supports and documents reports per state APS/Ombudsman requirements
For detailed security controls → read references/security.md
6. Output Format Defaults
Specs: Goals → Non-goals → User stories → Data model → API routes → Security → Edge cases → Test plan → Rollout plan
Code: File tree first, then each file in its own code block with filename header. TypeScript preferred.
Data models: DynamoDB: show PK, SK, GSI1PK, GSI1SK, and all attributes with types. RDS: show CREATE TABLE SQL with constraints.
API routes: Show method, path, auth requirement, request body, response shape, error codes.
Resource referrals: Program name → eligibility → how to apply → contact (phone/URL) → what to expect.
7. When to Read Reference Files
Load reference files on demand — don't load all at startup.
| User asks about... | Read... |
|---|
| Conversation flow, prompts, turn management | references/conversation-engine.md |
| Resident memory, context persistence | references/memory-capture.md |
| Risk scoring, engagement detection | references/engagement-scoring.md |
| Family notifications, outreach copy | references/family-outreach.md + references/message-generator.md |
| Voice calls, phone interface | references/voice-interface.md |
| Alerts, thresholds, routing | references/alerts-system.md |
| Staff UI, dashboard features | references/caregiver-dashboard.md |
| Group activities, social features | references/community-features.md |
| Reports, dashboards, metrics | references/analytics.md |
| Push/email/SMS delivery | references/notifications.md |
| MCP server, tool schemas | references/mcp-tools.md |
| OAA, Medicare, Medicaid, AAA, Meals on Wheels | references/aging-services.md |
| Tenant setup, isolation, config | references/multi-tenant.md |
| Login, SSO, SAML, Clerk, Cognito | references/auth.md |
| Subscriptions, metering, invoices | references/billing.md |
| CDK, Lambda, ECS, deployment | references/aws-deployment.md |
| GitHub Actions, deploy pipeline | references/cicd.md |
| HIPAA, encryption, audit, compliance | references/security.md |
| DynamoDB tables, RDS schemas, types | references/data-models.md |
| Mobile app, React Native, Expo | references/mobile-app.md |
| Module list, module specs (1–28) |
