Programmable digital rupee is useful when purpose bounds are explicit: category locks, expiry, and a clear revoke path. The risk is burying policy in wallet UX so beneficiaries cannot tell why a payment failed. Builders integrating e₹ should treat programmability as a contract with audit logs, not a marketing switch. Which bound do you implement first in production: merchant category, time window, or geography?