processdecisionsbuilding

What the anti-drift list actually is

April 2, 2026
1 min read

The anti-drift rules for BTA: no OAuth, no in-app dashboard, no multi-user accounts, no custom scoring.

Wrote them as constraints. Realized later they're not constraints — they're a list of decisions I'm not thinking about right now.

OAuth isn't off the table because it's wrong. It's off the table because I can't afford the cognitive overhead of getting it right before there's a reason to. Same with multi-user. Same with the dashboard.

The list is a record of deferred decisions, not rejected ones. Which means it needs revisiting when the conditions change — when a customer asks by name, when the market pulls in a specific direction.

Until then it's a boundary, not a verdict.