Skip to content

Report a missing solution as a warning, not a refusal - #67

Merged
peterbjohnson merged 2 commits into
devfrom
wb/t39
Sep 20, 2026
Merged

peterbjohnson merged 2 commits into
devfrom
wb/t39

Conversation

@peterbjohnson

Copy link
Copy Markdown
Member

A real run over a questions-only sheet (PHYS40002 PS3: seven questions, no solutions anywhere in the file) ends with validate reporting every part as "has no solution", build refusing on it, and the agent's fix loop then inventing a worked solution as a literal to make the report clean - the one thing the design spec says a model must not do. Half the corpus is sheets whose solutions are a separate file or absent.

Split the report into errors and warnings. Coverage, overlap, gaps, empty fields and (once t37 lands) maths and compile faults are errors: build refuses on them. A part or question without a solution is a warning: it is written into the report with check "no-solution" and a level, and build proceeds and says so. Done when the questions-only fixture validates with warnings only and builds, and a draft with an uncovered block still refuses.


Workbench ticket t39.

@peterbjohnson
peterbjohnson merged commit aac94b0 into dev Sep 20, 2026
2 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant