Record Repairer

Who the node is. The id is the key the DOT pins.

id

record-repairer

name

Record Repairer

type

agent

phases

Debugging

What it does, and the prose the agent is handed when the graph runs.

action29 words

Work the violation list field by field, mend only what the gate objected to, and send the record back for re-normalization instead of dropping it or writing it half-formed.

spec133 words

Work through the entries on violations one at a time. Each entry names one field and the specific constraint that field broke, and that constraint is your whole brief for what the value has to become, rewrite that field and leave every other field of the record exactly as you received it. Emit the mended record on repaired, whole: never emit a partial record, and never delete a field or blank it out to make a violation go away, because a silently dropped field is worse than a rejected one. When a violation cannot be mended from what the record itself contains, the value is missing rather than malformed, leave the field alone and note the reason on the record, so the next pass fails on something true instead of on your guess.in full above

model

claude-sonnet-5

agent

Repair worker

skill

skills/record-repairer.md

tools

none

mcp

none

params

max_retries: 2, temperature: 0.1

What arrives, what leaves, which nodes it expects to hear from, and what may not.

inputs

violations : json, record : json

outputs

repaired : json

dependencies

validate

cannot

no type is refused

will_not

emit a partial record, blank a field out to clear a violation

The keys the static analysis reads. Nothing here instructs the agent.

risk_markers

none

notes88 words

max_retries: 2 is the brake on the repair loop: two attempts beyond the first, three mends of one record in all, and past that the record is genuinely broken rather than dirty and grinding on it only burns tokens. Engine spec §2.6 counts the attempts that follow the initial execution, so the cap that reads as three attempts is written as two. Three mends sit inside the normalizer's three re-entries on the same cycle, which is what keeps the two caps from ending the loop at different times.

The card's own version, and who wrote it.

version

1.1.0

author

autogen

provenance

not stated