Live-ops compensation desk
Restores a raid’s lost items once.
Step 1 of 8
The agent you build
Ticket t-1Your agentInventoryrestore · moves items
Your agent reads a support ticket after a server crash and restores the items the raid lost.
Read the whole guide as text
- The agent you build. Your agent reads a support ticket after a server crash and restores the items the raid lost.
- 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 looks at what already happened, then acts once.
- Break it. The mistake: the agent sends the items to whoever reported the ticket, not to the ticket’s player. Geometer's result: Broke, rule restored-items-go-to-players.
- 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: one-restoration-per-ticket, restored-items-go-to-players). 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 liveops-compensation in the public agents repository.
Check your own agent like this
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.