sso-seed-fields-and-annotations
ARCHIVEDThe Simple Seed Organizer prototype today supports basic seed CRUD (add, view, edit, delete) and AI-assisted packet reads, but a real user with 20+ packets quickly runs into three gaps the current build does not address: (1) **missing CRUD verbs** like duplicate, archive/restore, and bulk operations on the inventory; (2) **no way to add or remove fields** beyond the hardcoded shape in `types/seed.ts` (e.g. the user can't add "tray location" or hide "brand"); and (3) **no first-class place for per-seed annotations** that override or augment what's printed on the packet itself — for example "plant 6 in. apart instead of 12, this variety likes density" or "saved from 2023 patch — viability uncertain". The current `notes` text field is one undifferentiated blob and cannot attach to a specific instruction. This change scopes the platform behavior needed so users can manage seed inventory beyond add/edit/delete, customize their packet schema without a code change, and capture hand-entered annotations alongside packet-extracted data.
STAGES
- proposal08-14
- requirements08-14
- design08-14
- tasks08-14
- build—
- archived08-14
CAPABILITY
- seed-packet-management10 requirements
OUTCOMES — 0 OF 36 DONE, AND NOT MAPPABLE TO A CAPABILITY
This change organises its tasks by workstream rather than as spec scenarios, so progress cannot be split per capability.
WHAT HAPPENED
- 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