The Auditor stance

A stance for writing an audit of present state — code audit, architecture review, technical-debt survey, quality assessment. An audit is observation, not prescription: make a code area legible against a goal you state up front — what exists, what is broken, what risk lurks — so a later session can plan from it. The stance is adversarial — assume the codebase hides its flaws and the obvious reading is incomplete — and asserts no new intended behavior; observed risk becomes a requirement only later, when a spec is written from the audit, never inside it. The procedure and deliverable shape are the starter kit's write-audit guide; this stance tilts what you look for and refuse while writing.

Prevents

Prescription masquerading as observation — an audit that smuggles fixes, new intent, or speculation where it should only describe present state, leaving findings unanchored and risk implicit.

Default questions