Release v0.1.4: MVP Database Schema, Constants, Validators & Services

12 February 2026

This release lays the foundational layer for the Calmony Sanction Monitor MVP.

What changed

• Database schema: Expanded to 12 tables — new tables for creditTransactions, screeningResults, screeningCertificates, and notifications. Existing tables (users, people, matches, auditLog) gained fields for credit balances, entity types, screening counts, match reasons (JSONB), reviewer tracking, and IP/user-agent logging. 4 PostgreSQL enums defined.
• Application constants (constants.ts): Credit pricing tiers, confidence thresholds, 30+ audit action types, status configs with labels and CSS classes, pagination defaults, certificate reference generator.
• Shared Zod validators (validators.ts): Input schemas for person CRUD, match review, credit purchases, screening, audit queries, bulk upload (up to 1,000 records), and CSV column mapping.
• Audit log service: Fire-and-forget createAuditLog(), request-aware createAuditLogFromRequest() (captures IP + user agent), and createBatchAuditLog() for bulk ops.
• Credit system service: getCreditBalance() with usage estimates, deductCredits() with atomic transactions, addCredits() with automatic bonus tier calculation.
• API route upgrades: All existing routes now use shared validators, constants, and services. Screening endpoint tracks duration and creates screeningResults records. Match review records status transitions. GDPR delete covers all new tables. Sanctions sync filters by isActive.
• Environment placeholders: Added Resend (email) and Stripe (payments) env vars to .env.example.

Why it matters

This is the internal foundation that all upcoming features — tRPC routers, CSV bulk upload, credit management UI, screening certificates, and email notifications — will build on. No user-facing UI changes, but the data model and service layer are now ready for the full MVP.

Technical notes

• Requires npm run db:push to sync schema changes
• Status fields use text columns (not enum columns) for backward compatibility
• New columns have sensible defaults (isMonitored: true, screeningCount: 0, isActive: true)
• No breaking changes to existing pages