FamilyForever™ V1 Certification
The gate is intentionally hard. A beautiful family experience is not ready for a real family until the privacy boundary and preservation promises are true in practice.
0 hard implementation blocker remains, plus manual production tests. Do not describe FamilyForever™ V1 as fully launch-ready yet.
Identity firewall
True Me uses an HttpOnly Secure SameSite=Strict session; family records are server-scoped.
Family graph ownership
Family links, facts, stories and interview records validate person ownership server-side.
Minor protection
Living minors are restricted to given name + relationship context in V1.
Interview consent
Interview creation requires explicit consent; question text is server-controlled.
Super Livd isolation
Anony-Me and True Me use separate server-side memory scopes and context rules.
Ask the Family
Answers are limited to preserved family stories; V1 explicitly refuses invention.
Pilot feedback
Feedback is optional, server-gated by True Me session, and does not collect family records.
Deletion boundary
True Me and Anony-Me are designed as independently deletable contexts.
Voice preservation
Consent-based browser recording and FamilyInterviewResponse.voice_file_url are now implemented. The remaining gate is real-device verification that uploaded audio is private, family-scoped and not publicly retrievable by URL.
Transfer completeness
The one-way TransferEnvelope bridge queues a private copy on the Anony-Me side only. True Me lists the owner’s waiting envelopes and explicitly imports or discards them; no True Me id crosses the bridge and no Anony-Me function writes Family tables.
True Me front door
True Me creation and entry now require the server-verified 6-digit Anony-Me Lock PIN. First-time setup creates the lock; subsequent entry uses PBKDF2-SHA256 verification with 5-attempt lockout and a 15-minute cooldown.
Adversarial device test
Production browser/device testing is still required for stale tabs, cookie/session expiry, cache isolation, private URLs and context switching.
What remains before the pilot gate turns green
- Verify the uploaded Family Interview audio is private and inaccessible across accounts/devices.
- Verify Base44 delivers the HttpOnly
livd_tmcookie to backend functions on real browsers/devices, including iPhone Safari. - Run the real browser/device adversarial test matrix with two test accounts and stale-tab scenarios.