# <project>: instructions for this repo

> One home per rule. A rule that binds everywhere lives here; a rule that binds one file type
> lives in .claude/rules/; background and provenance live somewhere this file links to.

## What This Repo Is

One or two lines: what this is, and what it is not.

## Architecture

The shape a reader cannot infer from the code in five minutes.

## Deploy

What a deploy IS here, and which command or push performs one.

## Quality Standard

What done means here, and what fails a change.

## User Context

Who this is for, and what they already know.

## Brand Voice Constraints

The copy rules that bind every surface.

## Build Commands

The exact commands, and what each one outputs.

## Key Files

The handful of files a newcomer has to read, and why each one matters.

## Rules paid for once

(Recurring sections this corpus carries that generalise. 14 headings recur in it; the ones tied to one project are counted on the page and left out of this file.)

- **Give every rule one home, and say which home by what the rule binds.** No date in the file: Rules that live in two places drift, and the stale half is read first.
- **A size limit belongs in a program that fails the file, not in a sentence inside it.** No date in the file: A budget written as prose is argued with; a budget written as a check is met.
- **A list an enforcement check reads lives in a data file beside it, never hardcoded.** No date in the file: A hardcoded list is edited by whoever is nearest, and the file stops agreeing with the check.
- **Correcting a fact means correcting every copy of it in the same pass.** Dated 2026-08-26 in the file: The intro of this file told readers to deploy one way while its own deploy section forbade that exact path.
- **Name the one working copy, and name the stale ones so a reader cannot pick the wrong tree.** No date in the file: One wrong pointer in an abandoned copy sent a whole audit through the wrong codebase.
- **A verify command written into the file is itself a claim: run it before you write it down.** Dated 2026-08-21 in the file: Two versions of one check sat in this file returning zero on a healthy page, claiming coverage nobody had.
- **Write down which component owns a number, so the next session does not build a second one.** Dated 2026-08-09 in the file: Two scanners for one number disagreed by 927,031 lines, and the page would have shown whichever ran last.
- **When a thing broke twice in opposite directions, write the shape down, not the last fix.** No date in the file: Two fixes in opposite directions, because the file recorded the symptom instead of the design.
- **Record a reversal with its date, or the next session helpfully reverses it back.** Dated 2026-08-14 in the file: A parked product was put back in front of visitors by a session restoring what the file still called correct.

Target: under 200 lines, per the published guidance (https://code.claude.com/docs/en/memory).
A size limit belongs in a check that fails the file, not in this sentence.
