frenzymath/danus/synthesize-verification-report

Synthesize Verification Report

Produce the final verification output JSON and verdict.

Input Contract

Aggregate all findings you produced earlier in this verification session — the per-item records from the sequential check and the reference check, held in context. Each issue must include location and issue.

Procedure

1. Collect all critical errors and all gaps from previous checks.
2. Build a complete verification_report object with:

• summary
• critical_errors
• gaps

1. Apply strict verdict rule:

• correct iff critical_errors=[] and gaps=[].
• otherwise wrong.

1. If verdict is wrong, produce concrete non-empty repair_hints.
2. Self-check the JSON against its schema before emitting — do this by reasoning, not by calling a tool:

• verdict is exactly "correct" or "wrong",
• repair_hints is non-empty iff verdict == "wrong" (empty string when "correct"),
• every entry of critical_errors and gaps has both location and issue,
• the verdict is consistent with the rule in step 3 (any critical error or gap forces "wrong").

If the self-check fails, correct the object before continuing.

1. Write the final JSON to the run's result file and emit it as your final message.

The verify service injects the absolute path for this run — write to results/{run_id}/verification.json under the service-provided run directory ({run_id} is the Run_id given to you). The verify service reads this file back and returns it verbatim as the HTTP /verify response; you invoke no MCP tool to persist it. Stop only after the file is written and the same JSON is your final message.

Output Contract

Final output JSON:

{
  "verification_report": {
    "summary": "string",
    "critical_errors": [],
    "gaps": []
  },
  "verdict": "correct",
  "repair_hints": ""
}

If there is any error or gap, verdict must be "wrong" and repair_hints must be non-empty.

Tools

• None — you build, self-check, and write the report by reasoning. The final JSON

is written to results/{run_id}/verification.json; the verify service returns it as the /verify response.

(The verdict is the verifier's only output — no memory is written; the worker does all writing to global memory and the fact graph.)