harvest

name	harvest
description	Run an adaptive Egregore harvest from Codex when the user invokes /harvest or $harvest to elicit tacit context, preferences, positions, and team judgment.

Egregore Harvest

Native Codex Egregore skill. A harvest is a structured elicitation process that turns tacit context into durable organizational memory.

Parse

Accept a topic plus optional flags:

• --respondents a,b
• --seed path
• --resume id
• --mode blind|disclosed|comparative

Resolve the initiator from .egregore-state.json, then git config. Mint IDs as harvest-YYYY-MM-DD-topic-slug and harvest-YYYY-MM-DD-topic-slug-respondent.

State

Markdown is canonical. Persist under:

memory/knowledge/harvests/{date}-{slug}/
  manifest.md
  sessions/{handle}.md
  synthesis.md

Single-respondent harvests may use one flat markdown file when that is simpler. Every manifest records topic, intent, initiator, respondents, disclosure mode, status, seed paths, and role-sheet assumptions.

Connected mode may also call bin/graph-op.sh helpers, but graph writes are best-effort and must never block markdown state.

Process

1. Sync memory with bin/agent.sh sync.
2. If --resume is present, reload the manifest, sessions, and prior evaluations before asking anything new.
3. Build a role sheet for each respondent from memory/people/*.md, recent handoffs, wraps, quests, and optionally graph context.
4. Clarify the harvest intent when topic, respondents, dimensions, or disclosure mode are under-specified. Use structured Codex question tooling when available; otherwise ask one numbered question at a time with .