# Helper examples can be insufficient for the caller

This repeats the existing compiler regression
`TestCalledBodyConstructionKeepsHelperAndCallerObligationsSeparate` using the
clean 0.6.11 candidate `60b1d7cb274f44531aa2501b00a29aed94b3958f`.
The compiler's [test source](https://github.com/kimjooyoon/meta-ontology-go/blob/fd91a3f099f7c65f3fed19d6c7e11b87b8d9b300/internal/bodyexecution/composition_called_bodies_test.go#L185)
already records this limitation. This is a direct CLI observation of that
existing example, not a new unseen-program experiment.

`Choose` has two permitted bodies, `x` and `x * 2`, and the local example 0 → 0.
Both satisfy that example. Fixed-order construction stops after selecting the
first body. `Main` calls `Choose(3)` and expects 6; the actual result is 3.

- Helper construction: 1/1 local cases, one attempted candidate of a two-candidate budget.
- Caller execution: 0/1 supplied expectations; actual 3, expected 6.
- Input separation: one disjoint root input, zero passing disjoint cases, PROGRESS.
- New inference: zero; this observation uses deterministic selection.

The command exited successfully and retained the mismatch as finite runtime
evidence. The CLI execution record, exact source, case file and build identity
are retained alongside this note. To reproduce with the identified compiler:

```sh
gooo body-compose --source ambiguous.gooo --cases cases.json --entry Main --out new-output
```

This identifies a language construction extension: a caller failure currently
does not automatically reopen an earlier helper choice that satisfied its own
examples. A future bounded joint search needs to preserve those local results,
record which caller examples became construction feedback, and evaluate the
changed combination separately. This note makes no claim that joint search
has been implemented.