forge-harness CLAUDE.md

forge-harness — Persistent Knowledge Hub

This file is the operational ruleset for AI (Claude Code). For human-facing guidance, see README.md. For command reference, see CHEATSHEET.md. For a first-time user asking «how do I use this», the answer is docs/USER_GUIDE.md — not CHEATSHEET (that is a reference to look things up in, not a document to read through). Blind floor-tier sim 2026-08-19 named exactly this: the header alone routes a beginner to CHEATSHEET, and only reading fh_detail_protocols.md corrects it.

forge-harness/
├── knowledge/             # Pure knowledge — timeless, for reference
│   ├── domain/            # Domain-specific knowledge
│   └── shared/            # Cross-project patterns
├── tracks/                # Project work history — accumulated over time
│   └── {project}/         # Per-project directory
├── CATALOG.md             # Global search index
└── CLAUDE.md              # This file (Sync/Push protocol)

FH is a 2-layer system: methodology layer (model-agnostic — tracks/, knowledge/, SKILL.md docs) + automation layer (Claude-native — agents, hooks, slash commands). The methodology layer is Codex-compatible (beta = validation maturity, not scope).

Running Claude Code in this project activates Control Tower mode.

Identity — 3-Layer Mission + Core Axis

The forge-harness hub is not just a repository — it is the command center for all Claude Code-connected projects in your local environment.

Doctrine (2026-07-12, operator-forged): a harness machinizes intent — it reads the human's intent and forges it into a machined form (AI-followable rules or deterministic code), via intent → forge → agreement (HITL) → machinery. Its payoff is relocating trial-and-error off the human (into the harness, run in parallel), so human time drops and attention routes to irreversible points. FH is the meta-harness and nursery: it incubates field harnesses (projects and new capabilities of existing harnesses) in its own sandbox — expensive per run, cheaper in total because trial-and-error pools and compounds — and emits them as independent specialized harnesses (shipped today as scaffold + approval machinery; the full chamber flow is the named target). Over other harnesses it operates in two modes: compose (cluster strengths) ∪ disrupt (melt and reforge via crucible; core invariants never melt). The nursery also verifies what it births: harness-verification core = the FH-native triad-consistency lens (spec↔implementation↔TC, cluster-independent) · extended = cluster instruments composed by UNION (knowledge/shared/harness-core/harness_verification_core_extended.md). Full doctrine: knowledge/shared/harness-core/harness_incubator_doctrine.md.