CLAUDE.md@engines/evidence-ledger · git:20260703.82d19fe · 2026-07-03 · sha256 287a5d6ba58f7e93
CLAUDE.md@engines/evidence-ledger git:20260703.82d19feA
Immutable. This exact content never changes and is served at /api/v1/blob/287a5d6ba58f7e93.
# CLAUDE.md - Claude Code Rules ## Project rules - Follow `AGENTS.md` in this repo. This file is the Claude Code-specific bridge; cross-harness behavior lives in `AGENTS.md`. ## Memory handoff The canonical memory owner on this repo is **claude**. Claude Code may keep local session context, but durable knowledge must be written as a Memory Handoff in `.claude/memory-handoffs/`. Full contract in `AGENTS.md`. At the end of any substantial task, check whether the session produced durable knowledge. If yes, write a handoff using `.claude/memory-handoffs/TEMPLATE.md`. Do not wait to be reminded. ## Brigade work loop (Mandatory) This repo is Brigade-wired. Route real work through Brigade so its outcome ledger fills. Invoke the `brigade-work` skill: `brigade work brief` at the start; run verifications via `brigade work verify run --target . --command "<test>"` (not raw) when the result should count; then `brigade outcome capture <skill-or-card-id> --run-id latest`; handoff at the end. If `brigade outcome rank` says "ranking: none", work is not flowing through Brigade. Full contract in `AGENTS.md`. For large scoping work, invoke `ultra-work-scout` first. It is installed with the built-in Brigade skills and keeps Scout delegation tied to verified Brigade work. ## Closeout - Report the exact verification command you ran. - If verification could not run, state the blocker. - If a Memory Handoff was warranted, confirm where it landed. ## Tool use - Say it = call it. If you say you will do something that requires a tool, call the tool in the same turn. Silent intent is a lie. - After a tool failure, emit a one-line status or call a different tool within 30 seconds. Do not silently reason for minutes. ## Git - Do not add `Co-Authored-By` or AI-attribution trailers to commits, PR bodies, or public docs. - Use conventional commits. - Never bypass pre-push hooks (`--no-verify`) unless the user has explicitly accepted the risk. - Never push to `main` directly on shared repos. Feature branch + PR. ## When in doubt - Default to reading more before writing more. - Ask one specific question rather than guess. - Surface tradeoffs rather than presenting decisions as facts.