fix
Inspect a client's domain and apply safe repairs to fix detected issues. Use deterministic checks to identify problems, then execute fixes while pausing for human approval when replacing existing records or making judgement calls.
Instructions
Check a client's domain, then repair what can be repaired safely.
check explains what is wrong. This acts on it. The same thirteen
deterministic checks run first and are still never decided by a model;
what a model decides is which repair to reach for, out of a set of tools
that cannot do anything else.
Anything that would replace a record somebody already published stops
and waits for a person. Approve it in the control room, or call
apply_mail_setup with approved=true. Creating a record that is
absent is not a judgement call and does not stop.
With agents off the checks still run and their findings still stand,
exactly as check degrades: only the repair needs a model.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes | A client name, or a bare domain. The same resolution check uses. | |
| dkim_selector | No | The DKIM selector to look for. Change it only if the client sends through something other than Resend. | resend |