LumenHealth is being reset as a clean open source hackathon monorepo. The new baseline is intentionally small: an Express API, a Next.js web app, a mobile workspace, and a Stellar service scaffold that contributors can build on milestone by milestone.
apps/api: Express + TypeScriptapps/web: Next.js App Router + TypeScriptapps/mobile: mobile product workspace scaffoldapps/stellar-service: Stellar service starterpackages/config: shared environment and workspace rulespackages/types: shared contracts for the MVP
The previous repository had grown into a specific product implementation. For the hackathon, we want a cleaner contributor experience:
- smaller surface area
- clearer architecture boundaries
- public-friendly documentation
- milestone-driven delivery
- issue-ready scaffolding for a 625-issue MVP backlog
We are rebuilding from first principles in this order:
- Authentication
- Clinic and staff management
- Patient records
- Encounters and clinical workflows
- Billing and Stellar integration
- Mobile offline and sync basics
- Demo hardening for hackathon launch
npm install
npm run check:architecture
npm run devCreate a root .env from .env.example before starting local services.
- Apps may import only
@lumen/configand@lumen/types. - Apps must not import from other app workspaces.
- Shared packages must not depend on app code.
- Public issue work should stay within a milestone boundary.
Run the boundary check before opening a PR:
npm run check:boundariesThis reset is a starting point, not the finished product. The current codebase includes:
- API boot scaffold with auth placeholder routes
- Web shell with hackathon positioning
- Mobile workspace placeholder
- Stellar diagnostics starter
- shared config and shared types packages
- contributor and issue-management documents