harvest-looplisted

A self-evolution pipeline that runs automatically after field sessions end. field-harvest (pattern extraction) → contention-layer (collision signals) → [Agent(subagent_type="challenger") + persona-innovator parallel] → synthesizer (challenger/innovator collision harvest) → Critic isolated Agent (SAGE automated critique) → harness-doctor (health check) → verify-bidirectional (consistency validation) → curator (skill lifecycle management) — 8 steps. Session learnings are automatically absorbed back into the FH ecosystem so the harness evolves on its own. In the main development environment, runs automatically at session end. For external FH users, proposes execution first. Triggered by "session harvest", "learning absorption", "fh evolution", or "harvest-loop". (The phrase "run the pipeline" is ceded to pipeline-conductor to avoid a trigger collision — for end-to-end verification sweeps use pipeline-conductor.)
chrono-meta/forge-harness · ★ 2 · AI & Automation · score 74

Install: claude install-skill chrono-meta/forge-harness

# harvest-loop — Field Session → FH Self-Evolution Pipeline > Automatically absorbs patterns/conflicts/discoveries from field sessions back into the FH ecosystem. > Internalizes as a pipeline the return loop from field projects to the harness that was previously done manually. > One of the core functions is real-time detection and blocking of **Semantic Drift** — where agent terminology gradually diverges in meaning as sessions grow longer. ## Operation Modes | Mode | Description | Trigger | |---|---|---| | **Forced mode** | Auto-runs at end of local development session. Executes without approval, only confirms final suggestions | Session wrap-up rules in hub CLAUDE.md | | **Lightweight mode** | Immediate harvest after Wave completion. Skip Steps 3/3.5/4 — prioritize fast recording | agent-composer Step 4-c (2+ new files or 3+ existing files changed, **or M-tier resolved**) | | **Proposal mode** | External FH users — confirms "run harvest-loop?" before executing | User utterance or `/harvest-loop` | **Simplification guard**: Sessions that only browsed/explored (no code changes or outputs) auto-skip even in forced mode. **Lightweight mode Done When**: ``` Step 0 (Regression Guard) + Step 1 (field-harvest) + Step 2 (contention-layer) + Step 5 (verify-bidirectional) complete + harvested pattern summary 1~3 lines output + "run full harvest-loop?" proposed (if patterns found) + [Card update prohibited] Do NOT update reference_next_session_starter.md in lightweight mode alone