seed-photos-as-collection

ARCHIVED

"I want to abandon the front/back model. I tried it, but it forces users to a) take more photos, and b) look too many places for information." … "Data gets read from both sides and populates a common set of fields." … "[A photo collection] is closer to what real gardeners will need, esp once you get into saved seeds and homemade packaging." — Katy, 2026-06-01

STAGES

  1. proposal08-14
  2. requirements08-14
  3. design08-14
  4. tasks08-14
  5. build—
  6. archived08-14

CAPABILITY

  • seed-photo-collection5 requirements

OUTCOMES — AND HOW EACH IS MEASURED

  • ✓1.1A user can save a seed with three photos and reload it with all three present in order, none marked front/backnot stated
  • ✓1.2A user viewing a legacy front/back seed sees its photos render unchanged on every surface (no data written)not stated
  • ✓1.3A user who edits and saves a legacy seed once has it upgraded to the photo collection in placenot stated
  • ○1.4A user who captures two photos for one packet gets one merged field set — no "back image evidence" panel, no F/B badges — **deferred to Change 2 (`seed-edit-photo-rail`); overlaps the rail redesign of this form**not stated
  • ✓1.5A user can browse the list, open detail, and run a batch import with all photos rendering correctly from the collectionnot stated

WHAT HAPPENED

  1. ARCHIVED

    proposal and specs and design and tasks and archive landed

    2026-08-14 · 1 pull request
    • #370chore(openspec): drain the change queue and collapse to one schema

History read from a manifest built at 2026-09-30 (09e7bcc).

1 pull request, found by commits touching the change folder