Product Guide
There is one product path: Project Marvin.
Marvin Engine is its synchronization runtime. It is not a second application to install.
Use This Path
- Install and open Project Marvin with
npm run marvin:installandnpm run marvin:ui. - Sign in through Microsoft Entra, or use the explicit loopback-only development sign-in locally.
- Add and authenticate each calendar account.
- Review privacy rules and validate access.
- Start the runtime after at least two calendars are Ready. The hosted process auto-starts with a saved profile; only connected and validated calendars are eligible for provider work.
Guides
- Getting Started
- Project Marvin application contract
- Platform support and maturity
- Azure Container Apps experimental adapter
- Onboarding and management UI
Deployment targets must consume the same Project Marvin runtime. The platform matrix is authoritative for whether a target is Supported, Tested, Experimental, or Planned.
Historical References
The research spikes and older solution folders are retained for credit and design history. They are not alternative setup choices, installers, or supported deployment paths.