Renewals paperwork engine: one page
What is built, what is proven, what is still ahead. The long version is the document-engine hub.
Oct 23, 2026, 14:40 UTC · renewals lane (session 005) · everything merged is dark; nothing is on at any customer
Clara can now build a renewal packet from a company's own recipe and park it, unsent, in AppFolio. Proven live at the Willows this morning in seven seconds, cleaned up after. Western Slope's exact shape ran at the Willows tonight and parked a correct draft too. The new-lease version of the same engine merged an hour ago. Turning any of it on is your call.
1 · The chain, and where each step stands
Sections 2 to 6: before/after, proof, what landed, what is next, waiting on you
2 · Before → after
Before (two days ago)
The team wrote every renewal addendum by hand in AppFolio. Term ends copied the old list, some mid-month. No read-before-write, no read-back. Learning a new customer's paperwork meant Fede typing the recipe.After (merged, dark)
Clara builds the packet from the company's recipe the moment the renewal decision is made. Term end is always month-end, everywhere, JP&Co included (a fix, no switch). The robot reads first, parks the draft unsent, reads the page back; a mismatch holds the packet with a plain reason. The learner read three customers' past paperwork read-only and drafted their recipes with zero manual work.3 · Proof at the Willows (this morning, 06:00 UTC)
Left: unit 101, no offer. Right: offer 375 parked, status "Not Sent", 12-month term 10/01/2027 to 09/30/2028 at $1,550, every typed value matching the order. Start to parked: 7 seconds. Then cancelled and reset; the lease keeps its packet record by design. A second run in Western Slope's exact shape (recipe v3, "original lease start" filled from our own lease record) parked offer 376 / document 900 at 22:26 UTC, read back as ordered, then was cancelled and reset. Screenshots on the hub.
4 · What landed, in plain words
| Piece | What it does | State |
|---|---|---|
| The door | The app's contract with the robot: read, cancel, park, send-parked, five possible answers, nothing writes on a mismatch. | merged |
| The engine | Versioned recipes per company, the print order, the three-rung ladder (team sends / Clara prepares / Clara sends). | merged |
| Month-end term | Every renewal term ends on the last day of the month, in the engine, the app and the rent math. | merged, live everywhere |
| Renewal caller | At the "prepare" rung the renewal workflow builds, reads, parks and records the packet on the lease. | merged + Willows proof |
| Western Slope shape | The three reads their one-page addendum needs, wired into the packet build; their recipe loaded as version 3. | merged + Willows proof in WS shape |
| New leases, same engine | New-lease sender setting (default off), robot park and cancel for new leases, and today the app workflow that builds, reads, parks and records a new-lease packet. | merged + Willows proof |
| Learn a customer's paperwork | Read past renewals through the robot, read-only, draft the recipe plus the office's questions. Western Slope reproduced the hand recipe; Situs (blind) found 27 blanks across 3 templates and 23 questions; Camellia 5 boxes and 11 questions. | run, read-only |
| Two must-close fixes | Co-applicants on one unit get one parked lease, not one each; a renewal's respond-by day never lands inside the new term. No switch. | merged + replays; co-applicants live at the Willows |
| Clara sends, tenant signs | Clara sent offer 377 herself; the test tenant signed it in the portal at 10:09am Denver; PropFlow saw the signature and cancelled the tenant reminder. Nobody countersigned; then cancelled and reset. Watch the 2:36 demo (learn, new lease, Clara sends, tenant signs). | Willows proof |
| Faded mass-text bubble | Removed from tenant threads, as asked. | merged |
5 · What's next, in order
6 · Waiting on you (one line each)
- Rotate the production Temporal API key? A builder's quoting slip printed it into a session transcript on this Mac (not committed, not posted). Recommend rotate.
- Two Western Slope gaps found tonight: the office's "respond by" day is not saved when a renewal starts from the outreach route, and AppFolio's pre-filled fields are still taken from the recipe's expected list instead of read. Both fixed and merged overnight: a renewal start now saves a "respond by" day (replayed read-only on 130 real Western Slope leases: 130 would have held before, 0 after), and the packet is built from the parts AppFolio actually pre-fills, read from the page. One follow-up left: a renewal started under 30 days before lease end can get a "respond by" day after the new term starts.
- Gera's "prepare" rung: Live only? Recommend yes.
- Approving in AppFolio counts as the human "send" decision? Recommend yes.
- Western Slope office questions for Kat and Jay (insurance email, "original start" blank, four pre-fill mismatches) whenever you choose to ask.