rl-docs-hub

Home · Apps · rl-bank-mvp

---

DB schema — card servicing + activity slice

Status: Draft, implementation-aligned for the current slice.

Existing collection updates

cards

Existing fields remain. This slice relies on and updates:

• status
• spendingLimit
• updatedAt

No destructive schema rewrite is required.

Existing collection reuse: audit_logs

Purpose in this slice:

• durable audit/activity source for customer card servicing actions without adding another event collection yet

Relevant document shape already present:

• id: string unique
• actorType: string
• actorId: string
• action: string
• entityType: string
• entityId: string
• metadata: object
  • title
  • description
  • accountId
  • previousValue
  • nextValue
  • debugCorrelationId
• createdAt: date

Query pattern for this slice:

• customer-scoped card servicing activity reads audit_logs where actorType=customer, entityType=card, and action=UPDATE

New collection: notifications

Purpose:

• lightweight in-app customer notification inbox

Suggested document shape:

• id: string unique
• customerId: string indexed
• title: string
• body: string
• level: string
  • INFO
  • SUCCESS
  • WARNING
• relatedCardId: string | null indexed
• relatedAccountId: string | null indexed
• relatedTransactionId: string | null indexed
• debugCorrelationId: string | null indexed
• readAt: date | null
• createdAt: date
• updatedAt: date

Indexes:

• unique id
• compound { customerId: 1, createdAt: -1 }
• compound { customerId: 1, readAt: 1, createdAt: -1 }

Derived activity model

publicListMyActivity is a projection layer, not necessarily its own collection.

It may combine:

• audit_logs
• notifications
• transactions
• card issuance/activation state from cards

Account history realism notes

This slice does not add a new collection.

accounts

Derived API fields come from existing stored fields:

• availableBalance
• currentBalance
• status
• openedAt

transactions

This existing collection remains the source for:

• last transaction time per account
• recent transaction count
• 30-day inflow / outflow aggregates
• recent account ledger history shown in the apps

No destructive schema change is required. The slice is intentionally projection-heavy rather than storage-heavy.

Staff account servicing support slice notes

This slice reuses existing collections only.

accounts

Relevant existing fields:

• id
• customerId
• accountNumber
• accountType
• currency
• status
• availableBalance
• currentBalance
• openedAt
• updatedAt

Behavior in this slice:

• staff servicing mutations update status and updatedAt
• no destructive schema rewrite is required

audit_logs

Additional metadata expectations for staff account servicing events:

• previousStatus
• nextStatus
• reason
• source = support_workspace
• customerId
• accountNumberMasked

Query pattern for support detail:

• filter entityType=account and entityId=<accountId> ordered by createdAt desc

transfers

Used read-only for support context where:

• fromAccountId=<accountId> or toAccountId=<accountId>

notifications

Used read-only for support context where:

• relatedAccountId=<accountId>

Data retention note

Because this is fake-bank demo data, retention can stay simple for now. If the volume grows later, activity and notification retention policy can be documented separately.