State the per-verb marker/exit contract: generalize's partial failure bypasses the warning/exit-3 convention #325

New Issue

2026-07-24T00:06:17+02:00

claude commented

2026-07-24 00:06:17 +02:00

Field evidence (milestone fieldtest "Surface honesty on stderr", 2026-07-24, source-blind against the release binary): partial or degenerate campaign failures do not surface uniformly across the family verbs.

sweep member failure → aura: warning: cell (…) failed … — recorded, campaign continues, exit 3.
walkforward all-folds-fail → aura: warning: walkforward cell failed …, exit 3.
generalize with one no-data instrument → aura: generalize produced no cross-instrument grade, exit 1, no warning: marker, and no per-instrument attribution — even though the other instrument in the pair had data and ran.

The C14 class-marker paragraph (shipped this cycle) defines warning: as a recorded fault the run survives, feeding exit 3; sweep and walkforward follow it, generalize does not. Ask: state the marker/exit contract per family verb in C14, and decide whether generalize's partial failure is a survivable warning-class outcome (per-instrument attribution + exit 3) or a legitimate hard refusal (then C14 should say why generalize is different).

Provenance: fieldtest spec fieldtest-milestone-stderr-honesty, survey capture in fieldtests/milestone-stderr-honesty/captured/example3_survey.log on the cycle branch.

Field evidence (milestone fieldtest "Surface honesty on stderr", 2026-07-24, source-blind against the release binary): partial or degenerate campaign failures do not surface uniformly across the family verbs. - `sweep` member failure → `aura: warning: cell (…) failed … — recorded, campaign continues`, exit 3. - `walkforward` all-folds-fail → `aura: warning: walkforward cell failed …`, exit 3. - `generalize` with one no-data instrument → `aura: generalize produced no cross-instrument grade`, exit **1**, no `warning: ` marker, and no per-instrument attribution — even though the other instrument in the pair had data and ran. The C14 class-marker paragraph (shipped this cycle) defines `warning: ` as a recorded fault the run survives, feeding exit 3; sweep and walkforward follow it, generalize does not. Ask: state the marker/exit contract per family verb in C14, and decide whether generalize's partial failure is a survivable warning-class outcome (per-instrument attribution + exit 3) or a legitimate hard refusal (then C14 should say why generalize is different). Provenance: fieldtest spec `fieldtest-milestone-stderr-honesty`, survey capture in `fieldtests/milestone-stderr-honesty/captured/example3_survey.log` on the cycle branch.

claude referenced this issue

2026-07-24 00:06:48 +02:00

Distinguish benign gate-emptied notices from cell-failure warnings on stderr #278

claude referenced this issue

2026-07-24 01:00:54 +02:00

Distinguish benign gate-emptied notices from cell-failure warnings on stderr #278

claude commented

2026-07-24 15:52:32 +02:00

Consolidated into #324 (tracker harvest, 2026-07-24)

Both issues cover the same C14 surface — which family verbs owe a note:/warning: marker on null/partial results, and which exit class those outcomes belong to — and they would ship as one cycle anyway. #324 is the carrier; this issue's survey (generalize's exit-1 partial failure bypassing the warning/exit-3 convention, with no per-instrument attribution) rides along there.

Derived orchestrator decision: merging trims tracker noise without dropping any ask; the full captured survey stays readable here.

## Consolidated into #324 (tracker harvest, 2026-07-24) Both issues cover the same C14 surface — which family verbs owe a `note:`/`warning:` marker on null/partial results, and which exit class those outcomes belong to — and they would ship as one cycle anyway. #324 is the carrier; this issue's survey (generalize's exit-1 partial failure bypassing the warning/exit-3 convention, with no per-instrument attribution) rides along there. Derived orchestrator decision: merging trims tracker noise without dropping any ask; the full captured survey stays readable here.

claude referenced this issue

2026-07-24 15:52:32 +02:00

Widen the zero-trade/null-result note beyond walk-forward: sweep, generalize, and the vacuous-mc case #324

claude closed this issue

2026-07-24 15:52:32 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Brummel/Aura#325