PathForward Tools · Halo family memory surface
Capture protected family memory
A calm, consent-forward space for preserving family structure, memories, source receipts, and keepsake readiness.
PathForward Tools
FamilyTrust walkthrough
How family memories stay protected
Use this as the first-capture guide: the memory is encrypted before saving, and later access is explained by consent receipts.
- 1
Your family key locks the memory here first.
Capture text is encrypted in the browser before it is saved.
- 2
The server stores the encrypted envelope and source metadata.
Original photos, videos, audio, and documents stay in the systems your family already uses.
- 3
Visibility follows the consent rule.
Private, family, selected-member, and deceased-member memories stay behind the matching visibility and consent checks.
- 4
Notifications stay count-only or link-only.
Email, SMS, WhatsApp, and digest nudges should point family members back to the app without sending plaintext memory content.
Memory journey
From prompt to protected keepsake
The expanded journey shows how capture, encryption, linked sources, review, consent, and locked keepsake readiness fit together.
- 1completed
Prompt
The app asks for one family-safe memory without asking anyone to upload originals.
- 2active
Capture
Family members add a note and optional source references that point back to where originals already live.
- 3completed
Encrypt
The memory is encrypted before storage so the server receives an envelope, not plaintext family history.
- 4completed
Link Sources
Photos, videos, audio, and documents remain in family-controlled systems while PathForward keeps metadata-only links.
- 5review needed
Review
If something is unclear, the review step can loop back to capture instead of guessing.
- 6locked
Consent
Private, selected-member, family-wide, and deceased-member care rules are checked before anything is surfaced.
- 7locked
Surface
Family-facing views explain why something appears and who else can see it.
- 8locked
Keepsake
Posters, books, cards, and prints stay locked until sources, consent, review, and commerce gates are ready.
Review-to-capture loop
Review can loop back to Capture when the family wants more context.
1. Prompt: A gentle prompt starts the story. The app asks for one family-safe memory without asking anyone to upload originals. 2. Capture: The memory is captured in the app. Family members add a note and optional source references that point back to where originals already live. 3. Encrypt: Your family key locks it first. The memory is encrypted before storage so the server receives an envelope, not plaintext family history. 4. Link Sources: Sources stay linked, not copied. Photos, videos, audio, and documents remain in family-controlled systems while PathForward keeps metadata-only links. 5. Review: A reviewer can ask for more context. If something is unclear, the review step can loop back to capture instead of guessing. 6. Consent: Visibility follows family consent. Private, selected-member, family-wide, and deceased-member care rules are checked before anything is surfaced. 7. Surface: Approved memories can be shown safely. Family-facing views explain why something appears and who else can see it. 8. Keepsake: Keepsakes wait for readiness. Posters, books, cards, and prints stay locked until sources, consent, review, and commerce gates are ready.