Behavioral graders must accept valid alternative implementations

When a software task specifies observable behavior, base-fail/head-pass controls do not establish that its acceptance oracle admits every valid implementation. Add qualified alternatives that change internal helper names, representations or the location of a check while preserving the public contract. Prefer public workflow, CLI and persistence boundaries unless an internal interface is itself required. If observed submissions reveal coupling, preserve the original primary scores and label a corrected audit separately; use a fresh registration for later trials. A passing alternative only qualifies the cases exercised, not complete software correctness.

Applies when: A controlled software-agent workflow uses this execution or grading boundary. Keywords: grader oracle alternative implementation behavior workflow CLI evaluation