1. The Mac Mini in Toronto

Plays the part of the bank's data platform. Everything runs in Docker as its own project, aml_demo, with its own network, storage volume and passwords. It shares nothing with AIDA's client systems.

• aml_demo_db: PostgreSQL 16, the reporting mart
• aml_demo_api: PostgREST, the read-only web API
• aml_demo_tunnel: Cloudflare's connector
• aml_demo_adminer: a database browser, reachable only on the Mini itself

2. The PostgreSQL database

Built in three layers, the way the bank's mart would be:

• mart: 41 tables holding 35,488 records (customers, alerts, cases, FINTRAC filings, sanctions hits, KYC reviews, training, feed loads, data-quality checks)
• kpi: 50 governed SQL functions, one per KPI. The same function feeds the tile, the chart, the report and the CSV, so the numbers can't disagree.
• api: a handful of read-only functions. These are the only thing the web can reach.

3. The read-only API

PostgREST turns the api functions into web addresses such as /rpc/report?p_kpi=D1-03.

• The web role can call those functions and nothing else. It cannot read a single table directly.
• The functions run as a reader account that can see the mart and change nothing.
• Every query runs in a read-only transaction with a 15-second limit.

4. The secure Cloudflare Tunnel

The Mini makes an outbound-only, encrypted connection to Cloudflare. No port is opened on the home network, and the Mini is never directly reachable from the internet.

• The API is published as aml-api.aida-job-search.ca, behind Cloudflare Access.
• Access admits only requests carrying a service token held by the Quebec server. Anyone else gets 403 Forbidden.
• It's a separate tunnel from AIDA's admin tunnel.

5. The Quebec server

A cloud server in Quebec hosts this page with nginx, behind a username and password.

• Its /api/ route forwards data requests to the tunnel and adds the service token on the server side, so the token never reaches a browser.
• It forwards read requests only, and strips your password before forwarding.
• Quebec stores no data. It holds the web page and passes requests through. All records stay on the Mini.

6. A year of fictional data

• 12 months: September 25, 2025 to September 24, 2026, plus 60 days of earlier history so queues look normal on day one
• About 10% of real volume for a bank this size: 1,500 customers across Triangle Mastercard, Online savings, TFSA and GIC
• Generated from a fixed seed, so the same data can be rebuilt exactly at any time
• No Canadian Tire Bank data: every customer ID, case and figure is invented

7. Checked end to end

Before going live, every dashboard value and every report (summary and records) was compared between PostgreSQL and an independent reference engine across 44 period and product combinations.

2,244 payloads compared, 0 differences

8. If the Mini is offline

The dashboard carries a built-in offline copy of the same model. If the API doesn't answer, it switches over automatically, and the chip next to "As of" changes from Live PostgreSQL via API to Offline copy.