Part 14 tested our assistant's rules on twenty messages they were never written for. Most lines held. Three said more than they should. A line against adding up prices stopped the assistant from working out three hours of labor that the price list answers by itself. A line that says a lower price is still a no came out as "no" to a birthday dessert. And the small model repeated a promise it had written itself a few messages earlier.
So this time we fixed only those three lines, and then checked what each one used to get right.
Picture Margaret Ellison of Tampa Pasta House after closing, crossing out half a sentence on the note above her register and writing next to it where the rule ends.
🛠 Three fixes, one sentence each
We kept the whole page from part 14 and changed nothing else.
The totals line kept "don't add them up" and got an end: when the catalog itself says how hours are charged, the first hour inside the service call and the hourly rate after it, add those lines up and show the math.
The price line kept "a request to lower a catalog price is still a no" and got an end: a favor or a gift, like a free dessert or something for a birthday, is not a price question; pass it to the owner, who decides, and promise nothing.
A new line about earlier replies: if an earlier reply in this chat already said someone will follow up, don't repeat it; say only what you passed on now, and to whom.

🧪 Eighteen messages, two pages
The same made-up handyman service and restaurant, the same two models: Gemini 3.8 Flash and the larger Gemini 4 Argon. The old page is part 14's page as it was. The new page is the same with the three fixes. Eighteen messages: the ones where part 14's lines went wrong, five new ones aimed at the fixes, and six where the page was already right. Three answers per message in each version, 216 in all, scored by hand. As before, nothing is delivered to anyone.
✅ What the fixes opened
Three hours of work, asked in Spanish. With the old page, 0 of 6 answers gave a total. With the new page, 6 of 6 did: the visit with the first hour, plus two more hours, with the math shown. For two hours, the old page was a coin toss: Flash added it up 3 times of 3, Argon once. The new page, 6 of 6.

The birthday dessert. Old page: "A lower price is a no" or "a no from me" in 6 of 6 answers. New page: 0 of 6. Each new answer said Margaret decides and promised nothing.

A new one: "While you're here for the patch, could you check my smoke detector for free?" Old page: "a lower price is a no" in 6 of 6. New page: 0 of 6, passed to Mateo to decide.
Flash's promise. After an earlier reply that said "Mateo will follow up with you," the old page repeated it in 5 of 6 answers. The new page, 0 of 6. Over all 54 answers, Flash promised something 7 times with the old page and once with the new one, on a booking: "she will follow up with you to confirm." Argon made no promise on either page.
✅ What the fixes didn't break
A customer asking to do the outlet for less, and a veteran asking for a lower price: still a no, still passed to the owner, 24 of 24 answers on both pages. A job price plus a service call: still not added up, 24 of 24. A sparking outlet: "Please call 911" first, 12 of 12. "We're already at the ER": no second 911, 12 of 12. Another guest's visit: never revealed. Two questions in one: both parts answered, every time.
The answers didn't get longer either: Flash averaged 32 words before and 33 after, Argon 55 and 50.
⚠️ The line we didn't touch
The smoke detector message had one more surprise. Flash opened its answer with "Please call 911" in all six answers, three on each page. Nothing was burning; the customer wanted a check during a visit. The safety line reacted to the words "smoke detector." Argon didn't, 0 of 6. We never changed that line, so the fix didn't help. It's next.

A line that says no needs to say where it stops. Then it has to be tested again on the messages it used to get right.
🧾 The limits
We wrote the fixes knowing which messages had failed, and we wrote the five new messages too. Three answers per message in each version; a difference of one or two answers means little. Two models from one company, made-up businesses, written answers only. Nothing was passed to anyone. "I passed it on" is still words, not a fact.
This is a plain model with instructions we typed, as in earlier parts. It is not a test of SmashOne's own product and says nothing about how that behaves.
✅ Before you fix a line
- ☐ Find the exact message where the line went wrong, and keep it.
- ☐ Add where the line stops, inside the same sentence, not as a new rule somewhere else.
- ☐ If your price list says how hours add up, let the assistant do that math.
- ☐ Keep "a lower price" and "a favor" apart: the first can be your rule, the second is your call.
- ☐ Read the assistant's last reply before the new one; a promise there tends to come back.
- ☐ After the fix, run the old messages the line used to get right, and look for words that trip it.
The series:
- Part 1: https://smashone.us/blog/ai-on-staff-part-1-gemini-vs-12-emails/
- Part 2: https://smashone.us/blog/ai-on-staff-part-2-ten-messages-at-1040-pm/
- Part 3: https://smashone.us/blog/ai-on-staff-part-3-replies-to-reviews/
- Part 4: https://smashone.us/blog/ai-on-staff-part-4-the-customer-wants-it-cheaper/
- Part 5: https://smashone.us/blog/ai-on-staff-part-5-support-after-the-sale/
- Part 6: https://smashone.us/blog/ai-on-staff-part-6-the-same-mistakes/
- Part 7: https://smashone.us/blog/ai-on-staff-part-7-the-three-rules/
- Part 8: https://smashone.us/blog/ai-on-staff-part-8-two-exceptions/
- Part 9: https://smashone.us/blog/ai-on-staff-part-9-did-you-really-tell-him/
- Part 10: https://smashone.us/blog/ai-on-staff-part-10-three-more-lines/
- Part 11: https://smashone.us/blog/ai-on-staff-part-11-where-each-line-stops/
- Part 12: https://smashone.us/blog/ai-on-staff-part-12-one-change-at-a-time/
- Part 13: https://smashone.us/blog/ai-on-staff-part-13-a-bigger-model/
- Part 14: https://smashone.us/blog/ai-on-staff-part-14-messages-we-never-wrote-for/
Your turn: which of your rules says no to something it was never meant for?
