The fix prompt is a different beast from the initial-validity prompt. You are not telling the agent how to build a filing; you are telling it how to change exactly one thing without disturbing anything else. Agents that get a vague fix instruction tend to produce diffs that touch labels, calc weights, and presentation arcs the reviewer never asked about, and every untouched-but-edited artefact is a regression risk.
Cite the exact validator code, message, file, and line on the first line of the prompt. "Validator output: [EFM.6.5.16] decimals="INF" not allowed - my-2025.xhtml line 1342." Specificity here saves the agent from guessing what the code means. An agent that has to interpret a code from a one-line summary is several times less accurate than one given the full context.
Scope the change explicitly. "Fix only this code; do not modify other arcs, labels, contexts, units, decimals, signs, or facts." The do-not-modify list reads paranoid the first time you write it, and it earns its keep on every subsequent prompt because agents will edit adjacent artefacts unless told not to. Treat the list as a contract.
Name the artefact. The ix:nonFraction with name="us-gaap:NetIncomeLoss" and contextRef="c-2025-Year" at line 1342 is unambiguous. The first nonFraction in the income statement is not.
Specify the desired post-state. "Replace decimals="INF" with decimals="-3" so it matches the existing scale="3" rounding to thousands. Keep all other attributes unchanged." If you can write the post-state down, the agent can produce it; if you cannot, you are not ready to prompt yet.
Ask for self-verification. "After the change, confirm the audit identity (canonical equals transform(rendered) times 10 to the power of scale times sign) still holds. Confirm no other validator codes are introduced." Agents that have been asked to verify their own output catch their own regressions; agents that have not, do not.
When the fix is non-trivial, ask for the unified diff before applying. A pre-apply diff lets you confirm the change is scoped to the named artefact. It is the cheapest insurance against the agent quietly improving seven lines you never wanted touched.
Cite the exact validator code, message, file, and line. Agents that have to guess from a code alone are less accurate.
Scope the change. 'Fix only this code; do not modify other arcs, labels, contexts, units, decimals, signs, or facts.'
Name the artefact. 'On the ix:nonFraction with name=ifrs-full:Revenue and contextRef=c-Group-2025...'
Specify the desired post-state. 'Replace decimals="INF" with decimals="-3" to match scale="3". Keep all other attributes unchanged.'
Ask for self-verification. 'After the change, confirm the canonical value remains the rendered text times 10^scale. Confirm no other validator codes are introduced.'
When in doubt, ask the agent to show the diff before applying.
# Example surgical fix prompt
Validator output: [EFM.6.5.16] decimals="INF" not allowed - my-2025.xhtml line 1342
Fix instruction:
On the ix:nonFraction with name="us-gaap:NetIncomeLoss" and contextRef="c-2025-Year" at line 1342, replace decimals="INF" with decimals="-3" so it matches the existing scale="3" rounding to thousands. Do not modify sign, scale, format, contextRef, unitRef, or rendered text. After the change, confirm the audit identity (canonical = transform(rendered) * 10^scale * (sign == "-" ? -1 : 1)) still holds.
Show the unified diff before applying.3 questions. Druk op 1 tot 4 om te kiezen, Enter om te bevestigen.
Door deze quiz af te ronden, markeer je deze sectie als voltooid.
Tip: kies met 1 tot en met 4 en bevestig met Enter.