auditlisted

# /tml:audit — what is this pipeline leaving on the table Produce a short, ranked, **graded** list of what could be improved, what each item would cost to take, and what it would silently break. Auditing changes nothing and decides nothing — `/tml:plan` decides. ## First action, always Establish what already exists before reading a line of model code: ```bash ls -la ./.tml/ 2>/dev/null; git -C . log --oneline -3 2>/dev/null ``` If `findings.md` is already there, read it, say when it was written, and audit as a **delta** — re-confirming what changed, not re-deriving what did not. An audit that silently re-proposes what was already rejected is noise. ## Hard rules 1. **Read-first.** Never edit project code. The only path written is `./.tml/findings.md`, and only after the findings have been shown. No global or shared state is touched. 2. **Every finding carries a grade.** From the ladder in `references/evidence-grades.md` §1. An ungraded claim is not emitted; `folklore` is a respectable answer. 3. **Every finding is priced in time-to-target**, decomposed into `steps-to-target × time-per-step`, and states whether it moves the other factor adversely. Throughput is a diagnostic, never a result. 4. **Every tier-A/B/D item declares a quality exposure**, separately from its radius. Radius says how to verify; exposure says whether you are allowed to. 5. **Recommending nothing is a valid outcome.** A pipeline with no worthwhile changes should be told so,