comprehensive-learning — Session Learning Pipeline

Single fire-and-forget skill running Phases 1–9 on all machines and Phases 10a+10 (cross-machine compilation + report) on dev-primary only.

Full phase specs: references/pipeline-detail.md — read it when you need signal sources, extraction rules, candidate formats, or state file details.

Mode-Based Routing

MACHINE=$(hostname -s 2>/dev/null || hostname | cut -d. -f1 | tr '[:upper:]' '[:lower:]')
case "$MACHINE" in
  dev-primary) CL_MODE="full" ;;
  dev-secondary) CL_MODE="contribute" ;;
  licensed-win-1|licensed-win-2) CL_MODE="contribute" ;;
  *) CL_MODE="contribute" ;;
esac
# All modes run Phases 1–9. Only 'full' runs Phase 10a (compilation) + Phase 10 (report).

Cross-Machine Data Flow

dev-primary git pull in Phase 10a picks up all machines' committed derived state.

Pipeline Summary

Run phases sequentially. Non-mandatory phases log failure and continue. Fatal failures in Phases 1 or 4 set _PIPELINE_EXIT=1. Phase 10 always runs via trap EXIT.

For phase details (signal sources, extraction rules, YAML formats): → read references/pipeline-detail.md

Session Design: Lean by Default

Sessions are pure multi-agent execution engines — all brain directed at the task. Analysis, maintenance, and learning are deferred to the nightly run.

Must NOT run standalone during sessions: /insights, /reflect, /knowledge, /improve, consume-signals.sh heavy analysis, ecosystem-health-check.sh, session-end-evaluate.sh scoring.

Stop hooks: one hook only, raw write, < 1 second. See WRK-304.

Scheduling

Crontab entry (dev-primary, 22:00 nightly):

0 22 * * * cd /mnt/local-analysis/workspace-hub && \
  bash scripts/cron/comprehensive-learning-nightly.sh \
  >> .claude/state/learning-reports/cron.log 2>&1

Script: scripts/cron/comprehensive-learning-nightly.sh — git pull is a hard gate; each rsync is independently || true.

Related

• workstations skill: machine registry and cron_variant fields
• WRK-299: implementation tracking | WRK-304: Stop hook cleanup | WRK-305: signal emitters
• WRK-303: Ensemble planning → Planning Quality Loop (in references/pipeline-detail.md)
• /insights, /reflect, /knowledge, /improve: individual pipeline stages
• scripts/planning/ — ensemble planning outputs harvested by Planning Quality Loop

Iron Law

No learning pipeline phase (/insights, /reflect, /knowledge, /improve) shall run standalone during an active work session — learning is deferred to the nightly pipeline, always.

Rationalization Defense

Red Flags

These phrases signal you are about to violate the Iron Law:

• "let me quickly run /insights before we continue"
• "I should capture this learning now"
• "running /improve won't take long"
• "the session is winding down anyway"