# Audits Where independent review reports **of this archive's own generated output** — the museum, the sync mechanism, the generator — get filed once they're produced, so a report doesn't live only in a session's scratchpad and evaporate when that session ends. That's exactly what almost happened to `museum/2026-07-21_independent-audit.md`: it was written to a session scratchpad, the session ended, and it sat unreachable until a later session went looking for it. This folder exists so that stops being a per-session accident. **This is for audits of the archive itself, not the app.** Audits of the RobCo U.O.S. app (game features, UI, code health, save integrity, etc.) already have a home: `planning/<version>/audits/`, synced in wholesale from the app repo's own `planning/` folder by `sync.ps1`. Nothing here duplicates that — if you're filing an audit of the app, it goes there, not here. This folder is only for audits that target something that exists in *this* repo and nowhere else: the museum generator, the generated site, the backup/sync mechanism. ## Layout ``` audits/<target>/<date>_<short-slug>.md ``` One subfolder per thing being audited — currently just `museum/`. Add a new one (e.g. `audits/sync/`) if something else in the archive gets audited; don't invent subfolders in advance of having anything to put in them. Filenames are date-prefixed so multiple audits of the same target sort chronologically without needing an index file to track order. Keep the filed copy close to the auditor's original text. Add a short header (date, target — including the exact commit or state audited, auditor, and the standing caveat below) and leave the findings themselves alone; this is a record of what the audit said, not a place to re-edit it after the fact. ## The standing caveat every filed audit should carry If the auditor was itself a Claude session, the filed copy should say so plainly, and should say that a Claude session auditing Claude-built work shares its blind spots — a clean result is weak evidence, not a clearance. See `museum/2026-07-21_independent-audit.md`'s header for the wording this convention expects. ## Wired into the museum — 2026-07-21, CLOSED `audits/` now has a `classify()` entry in `museum/generate.mjs`: ```js if (parts[0] === 'audits') return { area: 'standing', room: 'STANDING' }; ``` It folds into the existing `standing` area — the same fold-in pattern `memory-audit/` used for `memory` — rather than getting a new area/room of its own. Reasoning: `audits/` holds persistent, cross-release reference reports about the archive itself, exactly the kind of material `planning/_standing` already holds (that folder's own `REVIEW-living-os.md` is a review doc, not a forward-looking plan, so a review report fits the existing bucket without stretching it). Folding in means the STANDING TOOLS page (`standing.html`) picks up every file under `audits/` for free via its existing `area === 'standing'` filter — no new listing/room code needed for one audit file, and no site code beyond `classify()` had to change. Confirmed after regenerating: the lobby's condition report shows `UNCLASSIFIED: 0` (down from 2 before the fix), and both `audits/README.md` and `audits/museum/2026-07-21_independent-audit.md` appear under STANDING PLANS on `standing.html`, each reachable at its own `docs/audits/...html` page tagged `STANDING`.