# Working in <project name>

<Two or three sentences: what this repository is, what it owns, and the one
rule a collaborator must not break. Write for a capable newcomer — human or
AI — arriving with no context.>

Claude Code reads `CLAUDE.md`, not `AGENTS.md`. If you want one canonical
file, add a `CLAUDE.md` stub containing a pointer sentence and the line
`@AGENTS.md` so its contents are imported.

## Start here

1. `STATUS.md` — current state, active work, and blockers.
2. `<path>` — <the seam a newcomer should read second>.
3. `docs/decisions/` — accepted decisions and their reasons.
4. `git status --short --branch` before editing anything.

## Authority boundary

- This repository owns <the facts it is authoritative for>.
- `<sibling system>` owns <facts observed here but owned elsewhere>; cite or
  observe them, never fork them.
- Never add: credentials, customer data, raw logs, <other excluded material>.

## Repository map

```text
docs/        <purpose>
scripts/     <purpose>
<path>/      <purpose>
```

## Structural rules

- <The load-bearing invariant, stated as a rule: "X is the only path that
  mutates Y.">
- <A second invariant, if one exists. Delete this section if none do.>

## Verification

```bash
<the command that must pass before handing off a change>
```

Report observed results, not intended ones. A check that could not run is
unknown, never a pass.

## Scoped guidance

A nested `AGENTS.md` inherits this file and adds or overrides only the rules
for its subtree. Keep this table current if you add one:

| Scope | Local guidance |
| --- | --- |
| `<subtree>/` | `<subtree>/AGENTS.md` |