The problem is not “another calendar SaaS.” The problem is an urgent production meeting that
still has to go out of Outlook: issue text, ServiceNow Interaction/Incident numbers, severity,
SDLC environment and servers, attendees from the live developer roster. EUPM captures that, rewrites
the description with shared.llm.dispatch (MiniMax path SRM uses), optionally searches
Jira using SRM2’s per-user credentials (not a duplicate secret), and downloads a
high-importance .ics pre-filled with attendees. You send it from Outlook.
EUPM never sends. Attendees must exist in srm_developers. Servers must exist
in secp_server_registry. Tables eupm_meetings, eupm_templates,
eupm_settings are user_id scoped. If SRM2 has no Jira row, the Jira toggle returns no
matches — not a 500.
The product is a file you review. If you needed auto-send, this app is the wrong tool on purpose.
CSS mock of the capture form. Not Outlook Web, not ServiceNow.
Injection of random addresses is refused. Same honesty as ARCHITECTURE.md.
If you do not see a send button, that is correct.
EUPM does not own those tables. Empty registry means empty pickers.
Will not send. Will not invent hostnames. Will not duplicate Jira tokens. Templates stay yours.
Delaware/DoC-style incident calls where the invite must look official and still be human-sent.
No invented Zoom dial-in.
Login for /eupm/app. This page is not your meeting list.
Open EUPMRequires a MelTuc account. Create one free.
Emergency Urgent Production Meeting — one-click urgent Outlook meeting invites for production incidents. Health stays cheap. If this page disagrees with the signed-in app, trust the app — the product contract and tests enforce that rule.