Blocked Has to Override Normal Device Behaviour

A backend revocation is ineffective if the device keeps registering and calling because local state still says active.

The bench evidence for Blocked Has to Override Normal Device Behaviour forced a narrower explanation than the original assumption. The LOUP backend includes a blocked state so policy can stop a device independently of its last local configuration.

On the next authenticated status/config exchange, a blocked unit should stop normal calling and present an appropriate device state. The control has to be enforced below the contact-list UI so cached configuration cannot preserve unauthorized access.

Verification included both the happy path and the failure path because a feature that works once is not yet a production contract. Evidence marker: blocked-state.

Revocation must dominate cached entitlement. A control plane is only authoritative if endpoints obey negative decisions as well as positive ones. For a voice product, that kind of boundary discipline matters because audio, signalling and hardware symptoms often look deceptively similar.

Project evidence

LOUP engineering marker: blocked-state. This note records the design or debugging lesson without publishing device credentials, private keys, customer data or manufacturing secrets.