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

Optimize/argmax axis: pick the best sweep point by a named metric (C12 axis 2) #67

New Issue
Closed
opened 2026-06-14 23:08:29 +02:00 by Brummel · 0 comments
Brummel commented 2026-06-14 23:08:29 +02:00
Owner
Copy Link
Copy Source

C12 names four orchestration axes; only axis 1 (grid sweep) ships. Axis 2 is optimize: over a SweepFamily, select the point that maximizes (or minimizes) a named RunMetrics field. The machinery already exists — aura-registry's rank_by (lib.rs) ranks reports by metric — so this is a thin layer, not a new execution core.

Build

  • An optimize(grid, metric, direction) entry (or a SweepFamily method) returning the winning point and its RunReport.
  • Reuse rank_by; do not fork the sweep executor.
  • CLI surface consistent with aura sweep / aura runs rank.

Acceptance

Deterministic argmax over a known small grid; ties broken deterministically (document the rule).

Contracts

C12 axis 2, C18 (rank_by). The smallest of the family axes — reuses the existing sweep + registry. Independent of seed/MC/walk-forward, so it can land early.

C12 names four orchestration axes; only axis 1 (grid sweep) ships. Axis 2 is *optimize*: over a SweepFamily, select the point that maximizes (or minimizes) a named RunMetrics field. The machinery already exists — aura-registry's `rank_by` (lib.rs) ranks reports by metric — so this is a thin layer, not a new execution core. ## Build - An `optimize(grid, metric, direction)` entry (or a SweepFamily method) returning the winning point and its RunReport. - Reuse `rank_by`; do not fork the sweep executor. - CLI surface consistent with `aura sweep` / `aura runs rank`. ## Acceptance Deterministic argmax over a known small grid; ties broken deterministically (document the rule). ## Contracts C12 axis 2, C18 (rank_by). The smallest of the family axes — reuses the existing sweep + registry. Independent of seed/MC/walk-forward, so it can land early.
Brummel added this to the The World, part II — orchestration families milestone 2026-06-14 23:08:29 +02:00
Brummel added the feature label 2026-06-14 23:08:29 +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 The World, part II — orchestration families
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#67
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?