Lamp & Light Creative Group
MissionReachAi · HVF Project Tracker
Updated September 17, 2026

Foundation is live. Walkthrough stays controlled.

MissionReachAi has moved from the initial demo into a hosted application foundation for Homeless Veterans Fellowship. The environment is intentionally limited to synthetic data, verified access boundaries, and non-sending workflows until HVF approves the next gates.

Application Hosted foundation deployed
Data posture Synthetic demo data only
Outreach No platform sending enabled
Current phase Week 1.6 readiness cleanup
Current phase

Phase 1.6 · hosted foundation hardening

This percentage is a conservative readiness estimate for the controlled pilot build, not a claim of launch readiness. The foundation is live, but HVF approvals, real data boundaries, client-facing polish, and HVF approval checkpoints still remain.

Demo concept
100%
Secure foundation
78%
Client-facing polish
46%
HVF approvals/data
22%
Pilot launch readiness
18%
Why the tracker is focused on foundation readiness

The project is no longer just a clickable demo. It now includes authentication, database connections, environment configuration, tenant boundaries, security controls, and deployment behavior that must be verified before broader pilot use. The safest next step is to keep the tracker current while access, roles, data boundaries, and approval rules are confirmed with HVF.

What is current today

  • MissionReachAi is deployed as a hosted application foundation for Homeless Veterans Fellowship.
  • The deployed environment is configured for controlled review with synthetic records only.
  • Core Phase 1 surfaces exist: dashboard, relationships, opportunities, drafts, tasks, imports, controls, audit evidence, readiness, and help.
  • The current application boundary is manual handoff only: drafts can support review and copy/mailto-style use, but MissionReachAi does not send outreach in this phase.
  • Final client-facing cleanup is still needed before using the live app for broader stakeholder review.
Live foundation verified Synthetic-only review No live outreach

Security foundation hardened

  • Invite-only access; no public registration.
  • Role-based permissions for admin, staff, reviewer, and auditor paths.
  • Organization-level data separation.
  • Secure environment-variable configuration.
  • Controlled database credentials and deployment settings.

Data safety boundaries

  • Synthetic sample records only in the current review environment.
  • No real HVF donor workbook imported.
  • CSV import remains dry-run/validated before confirmation.
  • Suppression, consent, and audit evidence remain preserved.

Fundraising controls

  • Human review remains required.
  • Drafts are reviewable and versioned.
  • Outreach is manual handoff only for Phase 1.
  • External providers remain disabled until approved.

Recent work completed

1
Hosted application deployed

Hostinger deployment issues were worked through, including production build settings, environment configuration, database connection, and dependency alignment.

2
Security posture kept conservative

No live outreach, real data import, autonomous AI, or external provider activation was enabled during deployment.

3
Client-facing scope corrected

Tracker language now reflects Homeless Veterans Fellowship while clearly labeling records as synthetic demo data.

Next safe actions

  1. Finish the final client-facing polish pass in the live app.
  2. Confirm HVF-approved users and roles.
  3. Confirm approved data fields and fields that must stay out of the system.
  4. Confirm the data owner and cleanup decision-maker.
  5. Keep this tracker updated weekly as the Phase 1 foundation is verified.

What HVF still needs to approve

Jon has confirmed that he should be the main HVF administrator and primary reviewer/approver during startup. Nothing donor-, sponsor-, foundation-, or grant-facing should move forward without his review.

  • Final Phase 1 user list and role assignments for Jack Brady, Jason Herron, Thair Phillips, the Finance Manager, and the IT assistant as needed.
  • Jon Graff will serve as the trusted HVF test user for startup access verification and role testing.
  • Current and past donor list, plus any priority prospects HVF wants to cultivate.
  • Approved donor/prospect fields and restricted fields.
  • Duplicate-resolution, stale-record, suppression, exclusion, and approval-required rules for existing major donors, current grantors, government funders, corporate partners, and personal board/staff relationships.
  • Operational owners for access, data cleanup decisions, backup, and review.
  • Provider/legal/security review before any external integrations or live outreach.

Weekly tracker focus

This tracker will be updated weekly to show the current state of the approved Phase 1 foundation: HVF access, reviewer approval flow, role boundaries, data-safety expectations, and which pilot records are safe to use. The goal is to keep progress visible without expanding into live outreach or additional scope before HVF approvals are in place.

Weekly scope update HVF approval flow Client-facing foundation