git:20260930.7432f87 to git:20260930.00d1e1e

4 added, 2 removed. Audit A to A.

---

name: rem-investigate-project

description: The steps for investigating a project's page, composed after rem-investigate when the subject is under projects/.

---

# Investigating a project

Why these rules: docs/rem-skills/rem-investigate.md

- **Sessions show intent, not repository state.** What the user asked for is not

what was built; check the files before saying anything shipped or passes.

- **The page's `Paths` may be read**, offline, as evidence: inside those paths

only, at most four levels deep and twelve relevant text files (README, docs,

manifest, the files a claim needs). The first path is the main checkout; never

a disposable worktree. No home directory, hidden files or credentials. Cite each

file you read as its own source.

- A `project-inventory` item lists candidate files, not their contents. A

directory name alone is not a project.

- Old files are not recent activity.

## What to produce

- Follow `rem-page-project`, skeleton headings exact. Close the `Overview` `text`

- fence, or write `Unknown — <what evidence is missing>`. An example file does not

+ Follow `rem-page-project`, skeleton headings exact. **`Overview` is required

+ when the material shows the architecture** (its parts and how work moves between

+ them): a closed `text` fence with arrows. Otherwise write

+ `Unknown — <what evidence is missing>`. An example file does not

prove an output. Current code is not a decision (local code ≠ a decision to stay

local).