Frank's Fed

UAT · Grandparent walkthrough

Grandparent walkthrough — non-technical adult scans QR, joins household, logs one feed

Phase 04 HELP-02 hard Open

Status

Open

Assigned

Unassigned

Started

—

Completed

—

Expected behaviour

Recruit one non-technical adult (not tech-industry, not involved in the build). Owner generates a single_session invite via Settings → Helpers → +. Hand iPhone B (fresh install, signed out) to the recruit. Start a stopwatch. Recruit taps either the Universal Link (if AASA team ID substituted) or uses the in-app scanner. Observe the full flow from QR scan to first committed feed log.

Total elapsed time from first device-touch to undo-toast on first feed log: under 120 seconds. No moment where the recruit asks "what does this word mean?". No banned words (session, permissions, token, alert, warning, error, failed, missed, violation, restricted, overdue) on any helper-visible screen.

Why human

Voice, tone, and onboarding speed cannot be evaluated by automation. A real non-technical person is the only way to confirm HELP-02 and success criterion 1 (MVP-Killer #3). Completion time requires a real non-technical person; no simulator can exercise AVCaptureSession or the Universal Link AASA path on production hardware.

Comments

No comments yet. Add one by editing the comments array in .planning/uat-state.json.

Evidence

No evidence attached. Drop screenshots into .planning/uat-evidence/phase-4-uat-01-grandparent-walkthrough/ and reference them in the test's evidence array.

Update this test

Pick yourself, then claim, comment, drop a screenshot, or close. Each action opens a PR against master; site reflects after merge + next /franks-fed-status-publish run. Mutations are audit-logged.

How to claim, comment, or close this

The mutable state lives in .planning/uat-state.json. Easiest path is to ask Claude Code in the project repo:

"Assign phase-4-uat-01-grandparent-walkthrough to Dave and add a comment: 'Running with Mum on Thursday, she has an Android so will use the QR scanner path.'"

Or hand-edit .planning/uat-state.json directly. Drop screenshot evidence into .planning/uat-evidence/phase-4-uat-01-grandparent-walkthrough/ and reference the filename in the evidence array. Once the test passes or fails, set status to pass or fail with completed_at + a closing comment, then run /franks-fed-status-publish.

Source artefact: .planning/phases/04-helper-system/04-VERIFICATION.md · verification index: 0 · SC: HELP-02