Safety
The limits matter more than the idea.
Operational knowledge about private premises is sensitive. These constraints are stated first, because a memory layer that cannot be trusted should not be built.
What this is not
Excluded- No public database of private entrances
- No real personal information in this prototype
- No continuous driver tracking
- No employee-performance scoring
- No facial recognition
- No automatic blame assignment
- No permanent record without an explicit retention basis
- No production security claims
- No public access-risk scores for private properties
- No public ranking of difficult customers or addresses
- No automatic blame assignment
- No permanent negative property labels
- No reuse outside the permitted delivery context
- No driver-performance scoring
- No silent acceptance of conflicting reports
- No precise private entrance information shown without authorisation
- No public charging-network reliability league table
- No public naming or scoring of charging operators
- No permanent negative charging-site labels
- No claim that a charger is working when the status source is uncertain
- No pretence of live charging status where none exists
- No collection of unnecessary vehicle telematics or battery data
What any production system would require
Required- Sensitive-location exclusions
- Participant correction and dispute rights
- Role-based access required in any production system
- Independent security and privacy assessment required
- Data minimisation
- Clear deletion and expiry
- Location precision displayed honestly
- Recipient correction, expiry and dispute rights retained at all times
- Charging status always labelled with its source and time observed
- Temporary charging reports expire in hours, not indefinitely
- Site operators able to correct physical measurements about their own site
This prototype does not provide navigation, proof of delivery, regulatory compliance or production data security.