One family. One device. Fresh proof.
Short-lived code, authenticated family owner, single-use completion, and explicit child-device identity.
PAIR_CREATED → PAIR_CLAIMED → DEVICE_TRUSTED Interactive product prototype
Don't read the promise.
Run the family system.
This clickable demo pairs GetZ Parent and GetZ Child. Choose a journey, act on either phone, and watch the other side respond.
SIMULATED DATA · NO ACCOUNT REQUIRED · NOTHING IS SAVEDGETZ PARENTLIVE FAMILY EVENTSGETZ CHILD
CAREGIVER VIEW
PAIRING
Connect Alex's device
Enter the one-time code shown on GetZ Child. It expires in ten minutes and can only be used once.
✓
Fresh trust onlyThe code does not reveal another family or reuse an old session.
CHILD VIEW
READY TO PAIR
Join your family
Show this one-time code to your parent. They cannot pair a different device after it is used.
482913
Expires in 09:42LIVE EVENT LEDGER
What both apps agree happened—without exposing more than the family needs.
01
Family createdRivera family · owner verified
RECORDED02
Device pairingWaiting for code confirmation
OPENTHE BUILD BLUEPRINT 07
This demo is the contract.
The apps must tell the same truth.
Each journey defines the state, event, acknowledgement, recovery path, and privacy boundary the production iOS and Android systems need to implement.
No false green state.
Active, Limited, Offline, and Needs Attention are separate states with freshness and recovery instructions.
DEVICE_CHECKED_IN → STATE_EVALUATEDContext survives the handoff.
Amount, category, reason, decision, and expiry remain attached to one durable request.
REQUESTED → DECIDED → APPLIED → EXPIREDPurpose visible. Drafts private.
Families see mode, time, and shared reflection while the learner keeps appropriate working space.
SESSION_STARTED → REFLECTED → CLOSEDAcknowledgement closes the loop.
The event cannot disappear from a swipe or notification tap. A caregiver must explicitly respond.
HELP_OPENED → ACKNOWLEDGED → RESOLVEDUnknown is shown as unknown.
Stale check-ins downgrade protection status and give both sides specific recovery steps.
HEARTBEAT_STALE → ATTENTION → RECOVEREDYOU HAVE NOW SEEN THE SYSTEM
Next, we turn each journey into production acceptance tests.
The prototype is deliberately explicit: every visible state can become a testable requirement for GetZ Parent, GetZ Child, and the shared backend.
Send demo feedback ↗