Brummel/Aura
1
0
Fork 0
Code Issues 31 Pull Requests Actions Packages Projects Releases Wiki Activity

generalize metric applicability: --metrics tag + correct refusal prose for R-denominated-but-unranked metrics #207

New Issue
Closed
opened 2026-07-04 01:52:43 +02:00 by Brummel · 0 comments
Brummel commented 2026-07-04 01:52:43 +02:00
Owner
Copy Link
Copy Source

Fieldtest cycle-0108 F8: no surface says WHICH of the 17 metrics std::generalize accepts (the registry's 4-name R-expectancy family: expectancy_r, net_expectancy_r, sqn, sqn_normalized). --metrics tags only rankable|gate|annotation. Worse, the refusal prose calls max_r_drawdown — an R-DENOMINATED drawdown — a 'pip metric' ('gross/net R families generalize; pip metrics do not'). Fix: (a) add a generalize applicability tag to process|campaign introspect --metrics, derived via aura_registry::check_r_metric (no new roster site, #190); (b) correct the refusal prose to name the real rule (the rankable R-expectancy family generalizes) without mislabeling R-denominated metrics. Repro: aura campaign run fieldtests/cycle-0108-annotator-stages/c0108_probe_generalize_maxrdrawdown-based-campaign (see FINDINGS F8).

Fieldtest cycle-0108 F8: no surface says WHICH of the 17 metrics std::generalize accepts (the registry's 4-name R-expectancy family: expectancy_r, net_expectancy_r, sqn, sqn_normalized). --metrics tags only rankable|gate|annotation. Worse, the refusal prose calls max_r_drawdown — an R-DENOMINATED drawdown — a 'pip metric' ('gross/net R families generalize; pip metrics do not'). Fix: (a) add a generalize applicability tag to process|campaign introspect --metrics, derived via aura_registry::check_r_metric (no new roster site, #190); (b) correct the refusal prose to name the real rule (the rankable R-expectancy family generalizes) without mislabeling R-denominated metrics. Repro: aura campaign run fieldtests/cycle-0108-annotator-stages/c0108_probe_generalize_maxrdrawdown-based-campaign (see FINDINGS F8).
Brummel added the feature label 2026-07-04 01:52:43 +02:00
Brummel added this to the Research artifacts — process & campaign documents milestone 2026-07-04 01:52:58 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
BLOCKER
Core functionality blocked; preempts other selection
 bug
Observable misbehaviour
 feature
Substantial extension; no full spec required
 idea
Droppable; no commitment
No Label feature
Milestone
No items
No Milestone Research artifacts — process & campaign documents
Projects
Clear projects
No project
Assignees
Clear assignees
claude (Claude) Brummel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Brummel/Aura#207
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?