2026-05-21-emergency-pms-priority

activetype/meetingdomain/anabatic

Emergency call — PMS priority (2026-05-21)

TL;DR

Anabatic management flagged the Project Management System (PMS) as significantly behind schedule and directed the team to treat PMS as top priority, pausing other work unless it is urgent and important.

Attendees / source

  • Emergency call (evening 2026-05-21).
  • Direction from Anabatic manager (exact attendee list not recorded).

Decisions / directives

| Topic | Outcome | | --- | --- | | Priority | PMS first — deprioritize other projects that are not urgent/important | | Delivery pressure | Current PMS delivery is behind expectations; accelerate backend + contract alignment | | Cross-cutting UX | Plan to reuse Claim patterns for in-app chat and notifications (Portal uam DB) on PMS records | | Customer / Arsi | No Arsi API at launch — full customer input in PMS; m_customer in pms_schema (new prospects; Conexus is historical catalog only) |

Actions

  • [ ] Continue projects CRUD tracer against OpenAPI; close spec gaps (masters, category resolve, documents)
  • [ ] Track progress in vault hub and changelog (see [[Projects/anabatic-project-manager/changelog/2026-05-22-pms-progress-snapshot|2026-05-22 progress snapshot]])
  • [ ] Backlog: [[Projects/anabatic-project-manager/backlog/p1-import-claim-chat-notification-modules|Import Claim chat + notification modules]]

Related

  • ADR: [[Projects/anabatic-project-manager/decisions/adr-2026-05-22-pms-owned-customers-no-arsi]]
  • Hub: [[Projects/anabatic-project-manager/anabatic-project-manager]]
  • Claim architecture (Portal FCM + inbox): [[Projects/anabatic-claim/context/production-architecture]]