production-architecture

activetype/docdomain/integration

TL;DR

Claim production (first deploy 2026-05-18) shares the Portal program database for FCM tokens (Firebase) and the notification inbox table. Payment request creation still needs Conexus integration so the form can load the vendor list from authoritative company data.

Portal database (shared)

Claim connects to the Portal project database (vault hub: [[Projects/anabatic-sso/anabatic-sso]]; internal name Portal, path alias Projects/anabatic-sso/).

ConcernWhere it livesNotes
FCM device tokensPortal DBTokens from Firebase are persisted here for push delivery.
Notification inboxPortal DBIn-app notification inbox table used across internal apps.

Claim backends/services that send or surface notifications should treat this schema as shared infrastructure, not Claim-owned tables.

Conexus (payment request vendors)

When users create a payment request in Claim, the vendor picker must use Conexus as the company/vendor source of truth ([[Projects/anabatic-conexus/context/index|Conexus context]] — authoritative company directory).

  • Today: vendor list behavior may be local or partial; production payment-request flows need explicit Conexus read integration.
  • Backlog: [[Projects/anabatic-claim/backlog/p1-payment-request-conexus-vendor-integration|p1 — Payment request Conexus vendor integration]]

Related

  • [[Projects/anabatic-claim/changelog/2026-05-18-first-production-deploy|Changelog — first production deploy]]
  • [[Projects/anabatic-conexus/anabatic-conexus]]
  • [[Projects/anabatic-sso/anabatic-sso]]