Support compensation
Credits or refunds a ticket, never both.
Step 1 of 8
The agent you build
Ticket t-1Your agentHelpdeskcredit or refund
Your agent reads a helpdesk ticket and makes the customer whole with a credit or a refund. A ticket gets one or the other, never both.
Read the whole guide as text
- The agent you build. Your agent reads a helpdesk ticket and makes the customer whole with a credit or a refund. A ticket gets one or the other, never both.
- Your assistant builds it. Your own coding assistant builds the agent; Geometer does not build agents. With Geometer added as a tool, the assistant checks it right after.
- Watch it run. The agent as written reads the ticket, looks for earlier credits and refunds, then credits once.
- Break it. The mistake: the agent looks only for earlier actions of its own kind, not for the other kind. Geometer's result: Broke, rule credit-or-refund-never-both.
- The one-line fix. Put the original line back. That is the agent as written.
- Replay it, keep the check. The agent as written: no problems found within these limits (rules checked: credit-at-most-once, refund-at-most-once, credit-or-refund-never-both). Keep the check, and CI runs it on every change.
- Show others what was checked. Issue a report of what was tried and what held. It is opt-in and self-issued, and anyone can check it is unchanged with the open verifier.
- Take it. The agent is the folder support-compensation in the public agents repository.
Check your own agent like this
Read more
Recorded runs of the agent as written and with its one-line mistake; the result line is from the agent’s README. What a real check covers is in the alpha limits.