mansoq_notifications_be integration boundary

Declared component boundary

separate repository / optional app or service. Repository and route declarations do not prove this component is installed, enabled, certified or compatible with the current deployment.

Routes and installation

Plugin routes use their local URL declarations under the deployment-selected mount. Alternative core routes must not be combined as if simultaneously active.

Documentation evidence

• Currently supports
• Install
• Settings
• Token bookings (SMS)
• Service requests (in-app)
• Diagnostic reports (in-app)
• Encounters (in-app)
• Medication stock (in-app)
• Web push (in-app companion)
• API
• GET /in_app_notifications/
• GET /in_app_notifications/{id}/
• POST /in_app_notifications/mark_read/
• POST /in_app_notifications/mark_unread/
• GET /outbound_notifications/
• GET /outbound_notifications/{id}/
• GET /web_push_subscriptions/
• POST /web_push_subscriptions/
• POST /web_push_subscriptions/unsubscribe/
• GET /web_push_subscriptions/vapid_public_key/
• Click-through routing (frontend)
• Fields delivered
• resource_type → route
• Reference resolver

Review status

This article establishes repository/contract boundaries and does not prove installed capability, production credentials, regulator acceptance, security completeness or a validated click-by-click workflow.