SkieHow do we know a rule was really applied on a device?
After every apply, the device reads each protection back from Android and reports a compliance score. Skie does not assume a rule is in force because it was sent. It asks Android what is actually set, and anything that differs shows up against that device in the dashboard.
Many tools report that a policy was delivered. That is not the same as the setting being in force. A user could have changed something, an app could have reset it, or a manufacturer quirk could have ignored it.
Skie checks. When a policy applies, the device queries Android for the state of each protection: the filter, the hardening switches, the Chrome rules, the blocked installs and so on. It sends the results, signed with the per-device key, and the dashboard computes a compliance score for the device, which rolls up to group, branch, school and organisation.
You can run a compliance check on demand, and insights keep daily snapshots per group: readiness, fully compliant, average compliance, on latest policy, on latest app, online and silent share, low battery, and open events per device. Pattern detection compares the last seven days with the previous 28, with confidence labels and no claims about causes.
If a protection does not match, the device is flagged. Protections that can be reverted are re-applied, for example if someone resets all settings, and a breach event is raised at the right level.
Practical tip: use the score as a daily check, not an audit report. A printable compliance report is not available yet, but scores and history are visible, and the police report download covers lost devices.