stackchain/timmy-talking-turd
1
0
Fork 0
Code Issues 41 Pull Requests 6 Actions Packages Projects Releases 15 Wiki Activity

Implement separate opt-in training contribution and withdrawal flow #24

New Issue
Open
opened 2026-08-19 01:59:00 +00:00 by timmy · 0 comments
timmy commented 2026-08-19 01:59:00 +00:00
Owner
Copy Link

Parent epic: #3

Outcome

Let users knowingly contribute a confirmed image/label without coupling contribution to journal save.

Acceptance criteria

  • Journal save defaults to no training contribution.
  • Consent version and receipt are shown before contribution.
  • Withdrawal/deletion can address every derived artifact by contribution ID.

Dependencies

  • #22 — Finalize photo-analysis consent, retention, deletion, and privacy copy

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: #3 ## Outcome Let users knowingly contribute a confirmed image/label without coupling contribution to journal save. ## Acceptance criteria - [ ] Journal save defaults to no training contribution. - [ ] Consent version and receipt are shown before contribution. - [ ] Withdrawal/deletion can address every derived artifact by contribution ID. ## Dependencies - #22 — Finalize photo-analysis consent, retention, deletion, and privacy copy ## 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 M2 — Consented Dataset & Specialist Model milestone 2026-08-19 01:59:00 +00:00
timmy added the
type/feature
priority/P0
area/data
area/privacy
 labels 2026-08-19 01:59:00 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
area/backend

Application API and storage

  
area/data

Dataset and provenance

  
area/frontend

PWA and interaction design

  
area/model

Vision model and inference

  
area/privacy

Privacy and consent

  
area/release

Release engineering and distribution

  
area/safety

Clinical safety boundary

  
blocked

Blocked on an explicit dependency or decision

  
human-gate

Requires explicit human approval

  
priority/P0

Release-critical

  
priority/P1

High priority

  
priority/P2

Planned

  
state:review

   
type/docs

Documentation and evidence

  
type/epic

Roadmap epic

  
type/feature

Product feature

  
type/ops

Infrastructure and operations

  
type/research

Research or evaluation

  
type/security

Security hardening

  
type/test

Verification and quality gate

No Label
area/backend
area/data
area/frontend
area/model
area/privacy
area/release
area/safety
blocked
human-gate
priority/P0
priority/P1
priority/P2
state:review
type/docs
type/epic
type/feature
type/ops
type/research
type/security
type/test
Milestone
Clear milestone
No items
No Milestone
M2 — Consented Dataset & Specialist Model
Projects
Clear projects
No project
Assignees
Clear assignees
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#24
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?