For the truck owner

One truck on the board. Oil on the F-150 every 5,000 miles. Transfer-case fluid every 30,000 miles. Tire rotation every 7,500 miles. That is the whole list, and it lives on one due board.

You know the odometer. Last oil on the F-150 was at Miller's Indie Garage, 92400 miles and 94.50 on the invoice. The dash reads 94100, so 3,300 miles are left. Say those numbers to Muse once and the row is written. You drive about 1,400 miles a month. Book the shop for that week and the oil change happens before the miles run out.

Friday, ask Muse what's due on the F-150. Oil comes back with the 3,300 miles left and Miller's Indie Garage as the last shop. Tire rotation comes back with its own miles left: last rotate at 88000 and the dash at 94100 leaves 1,400 miles to the next 7,500 cadence. Transfer-case fluid comes back with its own leftover to the next 30,000. The Worker subtracts and names what is left, and no model sits in that path.

The calendar lines keep their dates and the mile lines keep their cadence. A late haul weekend does not slide the next tire rotation. A late errand is logged when it happened; the cadence does not drift.

Your shop preference is one ask too. Say it once: Always Ridgeway Truck Service on the F-150. Muse writes it, and the next oil booking starts at Ridgeway without you naming the shop again.

The board can call ChatGPT too. Subscribe once and ChatGPT hears when the miles you log put oil on the board, in a signed webhook naming the job and how late. You did not have to ask first.

The day the F-150 sells, say it once: sold. Muse archives the truck and the due board drops it that day. Every oil row, rotation line, and shop you logged stays in the history. If the deal falls through, one ask puts it back on the board.

The vehicle log on /vehicle-maintenance-log shows how odometer rows look. Copy the prompt on /for-your-agent and paste it into Muse. Free on Cloudflare Workers and D1.