​

Transaction categorization on Silvia Analyst

​

Non-invasive by design

• Two new tables, txcat_predictions and txcat_labels. Nothing existing gets a new column, trigger or foreign key.
• Ids that point at existing tables (transaction_id, category uuids) are soft references with no FK, so existing tables never depend on txcat. Dropping the two tables removes the feature.
• Phase 1 only reads existing tables. Users see nothing new.
• The tables live in public with a txcat_ prefix rather than their own schema, because a new schema has to be exposed in the Supabase API settings before supabase-js can reach it.

​

Pipeline

​

Tables

​

How it maps onto existing tables

​

Turning it on

1. Apply supabase/migrations/20260925_02_txcat_shadow.sql.
2. Set TXCAT_SHADOW_ENABLED=true (and optionally TXCAT_SHADOW_MAX_ROWS, default 500, at most 1000) in the environment.
3. Set TXCAT_MODEL_VERSION to the model behind the endpoint (default silvia-analyst-1.0). The served name (quant-analyst) is the same across versions, so this is the only thing that tells them apart. Each version predicts once per transaction, so a new version re-predicts recent rows and two versions can be compared on the same transactions.
4. The cron runs daily at 07:45 UTC. It needs QUANT_ANALYST_MODAL_URL and QUANT_ANALYST_MODAL_KEY; without them it returns skipped.

​

Reading the results

select
  count(*) as n,
  avg((p.predicted_category_uuid = l.final_category_uuid)::int) as model_acc,
  avg((p.baseline_category_uuid = l.final_category_uuid)::int) as plaid_acc,
  p.model_version
from txcat_labels l
join txcat_predictions p on p.id = l.prediction_id
where l.label_kind in ('user_edit', 'user_rule')
group by p.model_version;

​

Phase 2 (not in this PR)