harvest

# harvest Extract the repeatable procedure behind an unusually good result and land it as a reviewed cc-settings artifact — with the *evidence measured*, not asserted. The output is a concrete file (skill, rule, profile section, AGENTS.md diff, or team-knowledge note) plus a filled [harvest contract](./CONTRACT.md) whose verdict (PASS / FAIL / INCONCLUSIVE) decides whether it may be promoted, and to what scope. This is a **ratchet**: it only tightens shared standards on behavior it can show repeated or survived a trap. Behavior it cannot measure is marked INCONCLUSIVE and held back, not written up as fact. ## Standalone Codex source boundary Claude frontmatter does not create an isolated fork in standalone Codex. Keep evidence inspection read-only in the current context or use a fresh native reader. Audit native rules under `${CODEX_HOME:-$HOME/.codex}/rules`, the installed `AGENTS.md`, and managed artifacts in the real cc-settings git checkout named by the Codex sentinel's `repo_path`. Installed plugin/cache files and `darkroom/source` may be inspected for drift, but never edited as the source repo. ## Phase 1 — Witnessed behavior census Before deciding *what* to harvest, inventory *what was actually seen*. For each candidate behavior, record — from evidence, not memory: - **Witness count**: how many independent sessions / transcripts / runs showed it, and therefore **multi-witness** (≥2) or **single-witness** (1). - **What repeated**: the steps that were identical ...