StacksShared across all subject areas

Pilot

A solo learning build: enough to exercise the domain mechanics end to end without multi-tenant infrastructure.

Context

Postgres via Supabase, Python for data work, Next.js on Vercel, Claude Code for generation. Single synthetic tenant, no real customer data, no compliance obligations. Chosen for the shortest path from nothing to a working matching engine, with foundational decisions shaped correctly even where enforcement is deferred.

Stack fit96
  • Exact decimal arithmetic end to end — database column, ORM mapping, API serialisation and client. Floating point anywhere in the chain is disqualifying.
  • Certified periods must be immutable at the storage layer, not by application convention. No in-place update, no soft delete, and reopening must itself be an audited event.
  • Append-only, tamper-evident audit log with retention measured in years, held separately from application logging.
  • Authorisation must evaluate rules against the record's own history, not only the user's role. Plain RBAC is structurally insufficient.
  • Exchange rates must be effective-dated and keyed by convention. There is no single current rate.
  • Accounting date and system timestamp must be separate fields. The period an entry belongs to cannot be derived from when it was recorded.
  • Tolerance models must be trained per tenant. One tenant's variance distribution cannot inform another's.
  • Risk scoring models must be per tenant, with model artefacts and training data isolated to the same boundary as the tenant's transactional data.
  • Document-reading model calls must route to an endpoint in the tenant's permitted jurisdiction under a contractual no-retention guarantee.
  • Machine-generated narrative must carry provenance metadata and require human approval before it becomes part of the record.
  • Development requires synthetic data generators with deliberate error injection — missing entries, duplicates, wrong amounts, timing delays, fee variances.
  • Approval workflows must be durable and resumable across days, surviving restarts, deployments and approver absence without losing state.
  • and 84 more