SeedPass/CLAUDE.md

SeedPass Agent Guide

Overstory Ecosystem

This project is part of the Overstory multi-agent development ecosystem. When asked to "update Overstory" or work on the ecosystem, these are the relevant repositories:

• Overstory — The coordinator. Orchestrates multi-agent workflows across worktrees.
• Mulch — Structured expertise/memory system for agents.
• Canopy — Prompt management system for agents.
• Seeds — Git-native issue tracker for agents.
• os-eco — The entire Overstory ecosystem (meta-repo/docs).

Planning & Strategy

Consult these first to align with current objectives:

• Dev Control Center: Current priorities.
• TUI v2 Execution Plan: Roadmap for TUI v2.

Testing

Always run the full suite before proposing changes:

• bash scripts/run_ci_tests.sh
• Central Index: Test Infrastructure Inventory

TORCH Memory Integration

You have access to the TORCH memory system.

1. READ: Check .scheduler-memory/latest/${cadence}/memories.md for past learnings.
2. WRITE: Before exiting, save new insights to memory-update.md so future runs can learn from this session.

Project Expertise (Mulch)

This project uses Mulch for structured expertise management.

At the start of every session, run:

mulch prime

This injects project-specific conventions, patterns, decisions, and other learnings into your context. Use mulch prime --files src/foo.ts to load only records relevant to specific files.

Before completing your task, review your work for insights worth preserving — conventions discovered, patterns applied, failures encountered, or decisions made — and record them:

mulch record <domain> --type <convention|pattern|failure|decision|reference|guide> --description "..."

Link evidence when available: --evidence-commit <sha>, --evidence-bead <id>

Run mulch status to check domain health and entry counts. Run mulch --help for full usage. Mulch write commands use file locking and atomic writes — multiple agents can safely record to the same domain concurrently.

Before You Finish

1. Discover what to record:

   mulch learn
   

2. Store insights from this work session:

   mulch record <domain> --type <convention|pattern|failure|decision|reference|guide> --description "..."
   

3. Validate and commit:

   mulch sync
   

Issue Tracking (Seeds)

This project uses Seeds for git-native issue tracking.

At the start of every session, run:

sd prime

This injects session context: rules, command reference, and workflows.

Quick reference:

• sd ready — Find unblocked work
• sd create --title "..." --type task --priority 2 — Create issue
• sd update <id> --status in_progress — Claim work
• sd close <id> — Complete work
• sd sync — Sync with git (run before pushing)

Before You Finish

1. Close completed issues: sd close <id>
2. File issues for remaining work: sd create --title "..."
3. Sync and push: sd sync && git push

Prompt Management (Canopy)

This project uses Canopy for git-native prompt management.

At the start of every session, run:

cn prime

This injects prompt workflow context: commands, conventions, and common workflows.

Quick reference:

• cn list — List all prompts
• cn render <name> — View rendered prompt (resolves inheritance)
• cn emit --all — Render prompts to files
• cn update <name> — Update a prompt (creates new version)
• cn sync — Stage and commit .canopy/ changes

Do not manually edit emitted files. Use cn update to modify prompts, then cn emit to regenerate.