---
id: SEED-003
status: rolled-in
planted: 2026-05-12
planted_during: v1.7 Seamlessification / Phase 28 context
trigger_when: when relevant
rolled_into: Phase 25 (v1.8 Psyche Restructure)
rolled_on: 2026-05-18
scope: unknown
---

# SEED-003: Relocate working perches to be nested under their parent agent's perch

## Why This Matters

_To be filled in. Run `/gsd-capture --seed --enrich SEED-003` to add context._

Current layout: working/worker/subagent perches live as siblings of their parent agent's perch under `{SPT_HOME}/owlery/`. Nesting them under the parent (e.g. `owlery/doyle/workers/<worker-id>/`) would make ownership/lifetime relationships explicit, simplify cleanup on parent death, and make `$OWL list` output structurally tree-shaped.

## When to Surface

**Trigger:** when relevant

This seed will surface during `/gsd-new-milestone` when the milestone scope matches.

## Scope Estimate

**Unknown** — run `/gsd-capture --seed --enrich SEED-003` to estimate effort.

## Breadcrumbs

- `src/common/owlery.rs` — `is_worker_perch`, perch dir helpers (would change to be parent-aware).
- `src/owl/resume.rs:178` — `is_worker_perch` exclusion check; would need a "skip nested workers" sibling rule.
- `src/owl/resume.rs:140` (`inject_active_perch_context`) — flat `read_dir(&owlery)` iteration would become recursive or filtered.
- Phase 27 context — listener migration touched perch enumeration; useful precedent.
- Phase 18.4/18.5 binary handoff — handoff machinery enumerates perches; nesting affects discovery.

## Notes

_Captured via one-shot seed capture. Enrich with trigger, why, and scope at your convenience._

## Rolled Into

**2026-05-18** — Folded fully into Phase 25 (v1.8 Psyche Restructure). Phase 25 SC 7 covers worker-perch nesting alongside Psyche-perch nesting; shared migration + enumeration rewrite. No standalone phase planned. See `.planning/ROADMAP.md` Phase 25 block.