admin: recommendation log — per-tip explainability (features, policy, score, feedback) #67

New Issue

alvis · 2026-04-16T03:29:32Z

alvis commented

2026-04-16 03:29:32 +00:00

For every served tip: show (user, features snapshot, policy, ml score, feedback received, latency). Link to the full candidate set that was considered.\n\nRequires logging the feature vector + scores at decision time into a new tip_scores table or appending to tip_views. Keep for 30 days (GDPR).\n\nPart of the M1 admin console build sequence (step 10 of 16).

For every served tip: show `(user, features snapshot, policy, ml score, feedback received, latency)`. Link to the full candidate set that was considered.\n\nRequires logging the feature vector + scores at decision time into a new `tip_scores` table or appending to `tip_views`. Keep for 30 days (GDPR).\n\nPart of the M1 admin console build sequence (step 10 of 16).

alvis added this to the M1 — Real signal milestone 2026-04-16 03:29:32 +00:00

alvis added the admin label 2026-04-16 03:29:43 +00:00

alvis closed this issue

2026-04-16 03:56:24 +00:00

alvis referenced this issue from a commit

2026-04-24 15:10:18 +00:00

feat: M1 admin console — all 10 remaining pages + signal/quality/ops infrastructure

Sign in to join this conversation.