lease-auditlisted

# Lease audit Read a lease and its amendments. Establish what the documents actually say, decide whether the site is worth pursuing, and emit two things: | Output | What it is | |---|---| | **`<site>.deal.json`** | The deal file. **Authoritative.** Every downstream tool reads it. | | **`<site>-audit.md`** | The report a human reviews. Prose, with the arithmetic shown. | | **The financial model** | `financials.html` reads the deal file and produces it — a summary a director reads, the schedule from commencement to end of life, what each instrument did to the money, and what does not add up. Exports `.xlsx` for finance to reconcile a ledger against. | | **A completed audit form** | Where leadership asked for one. **The form is an input, not something you design** — whoever asks the question sets its shape, and the negotiator has no say in it. You fill it from the deal file, every answer traced to its instrument and section. `tools/auditform.html` does it deterministically and is the definition of how a field resolves; `forms/standard-audit-form.json` is a shipped example, there so the toolkit has all its pieces, and is meant to be replaced by the real one. | The first two, every time. The JSON is what the tools consume; the report is what makes the JSON reviewable; neither substitutes for the other. The last two are generated on demand from the first. **ORDER MATTERS, and the deal file comes first.** Write it, then hand it to a human for review in `review.html` — which list