For the motorcycle owner

One bike on the board. Oil on the CB500X every 4,000 miles. Chain cleaned and lubed every 500 on the odometer. Tire pressure on the calendar. That is the whole list, and it lives on one due board.

You know the odometer. Last oil on the CB500X was at Lakeside Honda, 18400 miles and 89.90 on the invoice. The dash reads 20150, so 2,250 miles are left. Say those numbers to Muse once and the row is written. You ride about 800 miles a month, which is close to three months of commuting. Book the shop for that week and the oil change happens before the miles run out.

Friday, ask Muse what's due on the CB500X. Oil comes back with the 2,250 miles left and Lakeside Honda as the last shop. Chain lube comes back with its own miles left: last lube at 19900 and the dash at 20150 leaves 250 to the next can. The Worker subtracts and names what is left, and no model sits in that path.

The calendar lines keep their dates. Tire pressure is the first Saturday of the month: gauge on the valve stems, both tires. The Saturday you gave up for a long ride does not push next month's check into the second week. A late weekend is logged when it happened; the cadence does not drift.

Your shop preference is one ask too. Say it once: always use Riverbend Motorsports on the CB500X. Muse writes it, and the next oil booking starts at Riverbend 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 bike sells, say it once: sold. Muse archives the motorcycle and the due board drops it that day. Every oil row, chain 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.