SYSE.51:4.2 - Construct observable decision points

Choose intermediate evidence the person or runtime can actually obtain: a violated constraint, disagreement that changes the action, an evaluator result, a missing decisive premise or a completed comparison. Specify how that evidence changes the next allocation. “Try harder if needed” is incomplete until need and the useful next move are recognizable.

A simple rule can select one cheap attempt, inspect its result, spend one bounded calculation on an unresolved consequential comparison, and otherwise finish or return the missing condition. A person’s short rule can be followed from visible conditions without calculating a numerical value of thought. A technical rule may choose model, sample count or branch depth. Preserve the current best supported partial result across those changes.

When search is used, distinguish ordering from exclusion. A heuristic score may choose which branch to inspect next; it cannot prove that an unvisited branch has no feasible solution. Sound exclusion needs the bound or predicate required by the chosen search Method. Several unsuccessful sampled routes show only those failures.