Problem
Changedoc mode still needs a principled way to validate changedoc truthfulness and implementation references, but this should not live inside the main E1..E{x} checklist gate.
Right now the immediate fix is to stop using changedoc quality as a default evaluation criterion. That leaves a separate follow-up question: how should changedoc verification work without consuming full coordination rounds or fighting the current workflow-tool semantics around submit_checklist and new_answer?
Goal
Design a separate changedoc verification path that does not consume full coordination rounds and does not rely on changedoc quality as a default evaluation criterion.
Scope ideas
- When and where validation should run
- Which checks are hard vs advisory
- How it interacts with workflow-tool semantics
- Whether changedoc needs lightweight additional structure
Non-goal
Do not solve this by keeping changedoc quality as a default checklist criterion.
Problem
Changedoc mode still needs a principled way to validate changedoc truthfulness and implementation references, but this should not live inside the main
E1..E{x}checklist gate.Right now the immediate fix is to stop using changedoc quality as a default evaluation criterion. That leaves a separate follow-up question: how should changedoc verification work without consuming full coordination rounds or fighting the current workflow-tool semantics around
submit_checklistandnew_answer?Goal
Design a separate changedoc verification path that does not consume full coordination rounds and does not rely on changedoc quality as a default evaluation criterion.
Scope ideas
Non-goal
Do not solve this by keeping changedoc quality as a default checklist criterion.