This brief gives a freelancer or technical partner a controlled first scope: receipt timeline, QR verification, selected sharing, WhatsApp-friendly links, export packets, and secure local-first behavior before advanced integrations.
The wallet does not contain all 14 platforms. It makes receipts useful.
Store receipts by year, type, status, issuer, and life event. Support search and filters.
Scan or open a receipt, show public verification status, and display the narrow claim.
Share a selected public-safe receipt link or QR image without exposing the private binder.
Create PDF/ZIP-style export for lawyer, institution, family, or personal archive.
Mark receipts private, shareable, family handover, lawyer packet, or institutional packet.
Keep selected receipt summaries available offline, with sync/export when online.
| Feature | Acceptance test | Not included in MVP |
|---|---|---|
| Import sample receipt | User can paste/import a sample VRX-1 JSON and see a readable card. | No production issuer backend required. |
| QR verification | Receipt card can show a QR code or open sample verification URL. | No government, university, or banking database integration. |
| Receipt timeline | User can filter by year, issuer, type, status, and privacy level. | No social network or messaging inbox. |
| WhatsApp share | User can share a public-safe text/link message. | No direct WhatsApp Business API integration at MVP stage. |
| Export packet | User can export selected receipt summaries as a simple PDF/JSON file. | No legal admissibility claim. |
| Security | No hard-coded API keys. Sensitive data not sent to AI providers by default. | No crypto wallet, token, or payment rail. |
I need a lightweight PlenaProof Vault MVP. It should import sample VRX-1 receipt JSON, display receipts in a year-by-year timeline, show QR/public verification links, support WhatsApp-friendly sharing of public-safe receipt summaries, and export selected receipt summaries as PDF/JSON. No production government/database integrations. No exposed API keys. No crypto features. The build should be simple, mobile-first, and easy to deploy as a web/PWA prototype.