Claude md Merge Instructions

# Merging the Brutal Honesty block into your CLAUDE.md

## Where to put it

**At the top of `CLAUDE.md`**, after any one-line preamble Claude Code expects
("This file provides guidance to Claude Code...") and BEFORE any project-
specific content (architecture notes, gotchas, language registry, etc.).

The block must be early because Claude Code truncates very long CLAUDE.md
files and you need the convention to survive truncation. Anything below the
brutal-honesty block is project-specific and can be re-derived; the convention
itself cannot.

## Conflict resolution if you already have a brutal-honesty section

Replace it. Do not partially edit. The v3.3 portable block is one atomic unit
and partial edits drift the doc out of sync with the rulebook — which is itself
L4 partial-with-claim-of-complete (claiming "we follow v3.3" when the
CLAUDE.md text is a v3.1 hybrid).

If you have local additions (e.g. project-specific evidence-rule examples, a
custom trigger phrase you want documented), put them in a SEPARATE subsection
BELOW the portable block:

    ## Brutal Honesty Convention (load-bearing — read first)
    ...portable block from claude-md-snippet.md verbatim...

    ### Project-specific addenda
    - In this repo, "production code path" specifically means [...]
    - Our smoke fixture is `tests/fixtures/foo.bin`; ceiling-tier exercises
      that are NOT yet using it land as Carried Debt entries with prefix `CD-`.

The portable block stays clean; your local color stays attributed.

## After pasting

1. Replace the line `See \`docs/conventions/brutal-honesty-rulebook.md\`` with
   the actual path you chose for the rulebook in your repo (the kit installs it
   to `docs/conventions/brutal-honesty-rulebook.md` by default — leave the line
   alone if you used the default).

2. Search your CLAUDE.md for any older brutal-honesty references (v1, v2, v3,
   v3.1) and delete them. Hybrid CLAUDE.md is a worse failure mode than no
   CLAUDE.md.

3. Commit the CLAUDE.md change in the same PR as the rulebook + scripts +
   templates so the doc and the executable enforcement land together. A repo
   that says "we follow v3.3" without `scripts/validate_pr_brutal_honesty.py`
   present is itself L4.

## What NOT to do

- **Do not paraphrase the block.** The exact wording of "100 ships, 0–99 does
  not" and `BHS_OFFICIAL = min(BHS_SELF_DRAFT, BHS_TIER_B)` are load-bearing
  for the validators — they search the rulebook for these exact tokens.

- **Do not move it to a separate file** and just link to it from CLAUDE.md.
  Skills and external links can fail to load; the convention is in CLAUDE.md
  precisely because CLAUDE.md is auto-loaded by Claude Code every session.

- **Do not "summarize for brevity."** A summary that drops the lie taxonomy
  reference, the trigger phrases, or the override-visibility clause is no
  longer the v3.3 convention; it is your own custom convention with v3.3
  branding, which is itself a §1 L4 violation.