Other

Migration Guide (v0.15 → v0.16)

REAP v0.16 is a complete rewrite built on the Self-Evolving Pipeline architecture. The lifecycle, genome structure, configuration, and vision system have all been redesigned. A guided migration tool handles the transition automatically.

Why Migrate?

Lifecycle redesigned: learning replaces objective as the first stage
Genome restructured into 3 focused files (application.md, evolution.md, invariants.md)
Vision layer with 3-tier memory for cross-generation context persistence
Merge lifecycle with genome-first reconciliation
File-based hooks replace inline hook configuration

Migration Steps

Step 1: Install v0.16 globally. This automatically deploys v0.16 skills and removes legacy v0.15 project-level skills.

bash

npm install -g @c-d-cc/reap

Step 2: Open Claude Code in your project and run the migration command.

bash

/reap.update

Step 3: Follow the 5-phase guided migration:

Phase	What Happens	Your Role
confirm	Shows what will change, creates backup at .reap/v15/	Review and confirm
execute	Restructures directories, migrates config/hooks/lineage/backlog	Automatic
genome-convert	AI reconstructs genome from v0.15 files into new 3-file structure	Review AI's work
vision	Set up vision/goals.md and memory tier files	Provide project direction
complete	Summary of migration results	Verify

Step 4: Verify the migration succeeded.

bash

/reap.status
/reap.evolve

What Changes

Area	v0.15	v0.16
Lifecycle	objective → planning → impl → validation → completion (5 phases)	learning → planning → impl → validation → completion (4 phases)
Genome	Multiple files, flat structure	3 files: application.md + evolution.md + invariants.md
Config	JSON-based configuration	YAML-based config.yml with cruiseCount, strictEdit, strictMerge, autoSubagent
Vision	No vision system	vision/goals.md + 3-tier memory
Hooks	Inline config	File-based: .reap/hooks/{event}.{name}.{md\|sh}
Environment	Single knowledge file	2-tier: summary.md (always loaded) + domain/ (on-demand)

Interrupted Migration

If the migration is interrupted (API error, session disconnect, etc.), progress is saved in .reap/migration-state.yml. This file tracks which phases have completed.

To resume: Run /reap.update again. It skips completed phases and continues from where it left off.

To restart: Delete .reap/migration-state.yml and run /reap.update again.

yaml

# .reap/migration-state.yml (example)
version: "0.16"
phases:
  confirm: completed
  execute: completed
  genome-convert: in-progress
  vision: pending
  complete: pending

Backup

All v0.15 files are preserved at .reap/v15/ during the confirm phase. This is a complete snapshot of your pre-migration state.

The backup is created before any destructive changes occur
After verifying the migration works (/reap.status, /reap.evolve), you can safely delete .reap/v15/
Keep the backup through at least one full generation to confirm everything works

Deprecated Commands

Several v0.15 slash commands have been renamed or consolidated in v0.16.

v0.15 Command	v0.16 Replacement	Notes
/reap.sync	/reap.knowledge	Manages genome, environment, and context knowledge
/reap.refreshKnowledge	/reap.knowledge reload	Reload all knowledge from disk
/reap.objective	/reap.run	Per-stage commands replaced by reap run <stage>
/reap.complete	/reap.run	Per-stage commands replaced by reap run <stage>

Legacy v0.15 project-level skill files are automatically removed during npm install. If any remain in .claude/commands/, they can be safely deleted.