Run a bounded private beta and synthesize correction/friction evidence #38

Open
opened 2026-08-19 01:59:02 +00:00 by timmy · 0 comments
Owner

Parent epic: #6

Outcome

Learn whether photo-first logging is fast, trusted, and worth repeating.

Acceptance criteria

  • Participants explicitly consent to beta data handling.
  • Report capture failure, completion time, correction rate, abstention rate, and retention.
  • Findings become bounded issues; raw medical imagery is not pasted into tickets.

Dependencies

  • #36 — Add private photo lifecycle controls to history and calendar
  • #37 — Ground Timmy chat answers in the local ledger with citations

Required evidence

  • Test or executable receipt attached to the issue/PR
  • Privacy/safety boundary checked where applicable
  • Clean checkout and relevant full suite pass

Delivery

Open a focused branch and PR with Closes #ISSUE. Do not include real medical images in issue comments or Git history.

Parent epic: #6 ## Outcome Learn whether photo-first logging is fast, trusted, and worth repeating. ## Acceptance criteria - [ ] Participants explicitly consent to beta data handling. - [ ] Report capture failure, completion time, correction rate, abstention rate, and retention. - [ ] Findings become bounded issues; raw medical imagery is not pasted into tickets. ## Dependencies - #36 — Add private photo lifecycle controls to history and calendar - #37 — Ground Timmy chat answers in the local ledger with citations ## Required evidence - Test or executable receipt attached to the issue/PR - Privacy/safety boundary checked where applicable - Clean checkout and relevant full suite pass ## Delivery Open a focused branch and PR with `Closes #ISSUE`. Do not include real medical images in issue comments or Git history.
timmy added this to the M3 — Private Beta & Longitudinal Value milestone 2026-08-19 01:59:02 +00:00
timmy added the
type/research
priority/P1
area/frontend
human-gate
labels 2026-08-19 01:59:02 +00:00
Sign in to join this conversation.
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/timmy-talking-turd#38
No description provided.