Prototype · Evidence confidence: High
TAMREVS
A privacy-first retail exit-verification concept that creates a temporary anonymous session, reconciles a shopper's journey and deletes the session after exit.
01 · Purpose
The problem
Retailers want to reduce theft without building persistent identity or biometric databases.
02 · Experience
How it works
Entry observations create an anonymous session; independent signals are associated with the journey and transaction context; exit observations produce a continuity decision rather than a persistent identity.
- Retailers
- Loss-prevention teams
- React 19
- TanStack Start
- Conceptual multi-sensor architecture
03 · Functional evidence
What actually exists
- Detailed system website
- Gate/session/decision UI components
- Threat/failure comparison
- Physical sensor integration and real-world accuracy not verified
- Controlled deployment
- Multi-factor sensor integration
- Retail trials
- Patent prosecution status
- Production false-positive rate
04 · Development
What remains
- Physical sensor integration and real-world accuracy not verified
- Controlled deployment
- Multi-factor sensor integration
- Retail trials
- Patent prosecution status
- Production false-positive rate
05 · Commercial
Business model
Licensing/pilot model is plausible; live revenue not verified.
06 · Intellectual property
IP position
Patent specification/application work is associated with the concept; legal status requires official document verification.
This archive records what the available project evidence says. It does not infer legal registration, patent grant, trademark ownership or regulatory status where that has not been verified.
07 · Assessment
Strengths and limitations
Strengths
- Privacy-centric problem framing
- Clear multi-factor architecture
Limitations / risks
- Hardware integration, accuracy, regulation and procurement remain substantial
08 · Evidence
What this record is grounded in
- GitHub repository: simonmowatt1-sudo/tamrevs
- Repository README / project brief where available
- Implemented home route where available
- Published Lovable URL recorded from repository metadata
A published URL means the project metadata records a deployment address. It is not represented as runtime-tested unless a separate verification pass confirms that deployment.
09 · Genealogy
Connections
Archive principle
Unknowns stay unknown until evidence changes them.Back to Project Galaxy