Technical detail · Mobile Phone Gateway Fundamentals
Release evidence and acceptance drills
The evidence pack shows that each chosen response works on the target phones. Keep the test result, visible response, and owner for recovery.
| Failure Mode | What Should Happen | Evidence to Request | Trap If Ignored |
|---|---|---|---|
| Phone absent / asleep | Source buffers or a fallback path covers the record. | Outage and movement acceptance drills. | Silent data gaps treated as “no events.” |
| Permission revoked | Degraded mode plus a user or operator notification. | Permission and background-mode test results. | The gateway stops without anyone noticing. |
| Duplicate source | Dedup by identity and sequence; idempotent upload. | Duplicate-record drill and dedup keys. | Inflated counts corrupt aggregates. |
| Storage full | Bounded buffer with a defined drop or stale rule. | Buffer policy with limit and stale threshold. | Unbounded growth bricks the app’s recovery. |
| Cloud rejects upload | Record the rejection and retest the contract. | Rejected-upload drill linked to the contract. | “Uploaded” is mistaken for “accepted.” |
Keep one release record with the boundary, allowed devices, mapping rules, and source and output samples. Include rules for time, units, quality, state, and identity. Record buffer and upload limits, access controls, and phone permission and background behavior. Test loss of link, movement, lost permission, duplicates, rejected uploads, and recovery. Save the results and name an owner for each issue.