SPROUT

Definition: An operational brief that is PRD-complete and ready to route to a session (or sessions) that will engage with the context provided to do work.

Characteristics: - Full brief structure: problem, constraints, success criteria, stage gates, output specs - Has a clear deliverable or outcome - Ready to dispatch — not a concept anymore, a work order - May route to one session or multiple coordinated sessions

Lifecycle: SPROUT → dispatched → work done → tagged with outcomes

Relationship to SEED: - A SEED may graduate to SPROUT when it’s time to operationalize - The SEED doc persists and gets tagged with promoted_to: SPROUT-XXX - The SPROUT doc gets tagged with promoted_from: SEED-XXX - Both continue to exist

Example:

# SPROUT: Tailscale SSH Fix — Phase 1 Diagnostic
**Filed:** 2026-05-13
**Status:** DISPATCHED
**Type:** SPROUT
**Promoted from:** SEED-XXX
**Assigned to:** [Session/Agent TBD]
**Problem:** Agents cannot SSH to Pi in non-interactive context due to Tailscale
  SSH intercept. Need diagnostic + viable workaround path.
**Success Criteria:**
  - [ ] Full scope of blocked operations documented
  - [ ] At least one viable workaround identified and tested
  - [ ] Recommendations for long-term access architecture written up
**Stage Gates:**
  - Gate 1: Confirm all blocked operations (test each: ssh, scp, rsync, git over ssh)
  - Gate 2: Identify workaround candidates
  - Gate 3: Test workaround in non-interactive context
  - Gate 4: Document findings + recommendations
**Output:** Brief document at ~/.pearl/seed-bank/sprouts/SPROUT-001.md
**Tags:** #infra #access #tailnet