selection-seed-stage

IN BUILD

"this rings true - lets work through the idea of beefing back up the selection machinery without losing the personal, human connection seeds that I write." "I don't want this to be the final decision or for hard coded architectural decisions to bite me later."

STAGES

  1. proposal08-21
  2. requirements08-21
  3. design08-21
  4. tasks08-21
  5. build—
  6. archived—

CAPABILITY

  • experiment-seed-stage5 requirements

OUTCOMES — AND HOW EACH IS MEASURED

  • ○1.1An idea is captured as a seed — a row exists at `Status = Ideation`not stated
  • ○1.2A seed records the moment rather than a category — its Why this mattersnot stated
  • ○1.3A seed is promoted out of Ideation — the incident test passes, a scorenot stated
  • ○1.4A seed that names no moment is held, not rejected — it stays atnot stated
  • ○1.5A seed stays off the public catalog — with `Public` unchecked it isnot stated
  • ○1.6A seed is visible to Katy in edit mode — listed carrying hub statusnot stated
  • ○1.7The seed stage is abandoned — deleting `docs/SELECTION.md` and thisnot stated

WHAT HAPPENED

  1. TASKS

    proposal and specs and design and tasks landed

    2026-08-21 · 1 pull request
    • #395docs(selection): add a seed stage above Explore

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

1 pull request, found by commits touching the change folder