Flat run registry: give 'aura run' a persisting path, or retire 'runs list'/'rank' #73
Reference in New Issue
Block a user
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?
After cycle 0045 (registry lineage for families, #70),
aura sweep/walkforward/mcpersist to the family store (families.jsonl); no CLI command writes the flatruns.jsonlanymore (aura run/--macd/--realnever persisted). Soaura runs listandaura runs rank <metric>remain in the CLI but read a store nothing populates — a live dead-end surface.The 0045 spec deliberately kept
runs listfor "standalone (family-less) runs only", but no command currently produces a standalone run record.Decision needed (design fork)
aura run(and--macd/--real) persist itsRunReporttoruns.jsonl— possibly always, or behind a--saveflag. This completes the spec's "standalone runs" framing and givesruns list/ranka live source.aura runs list/runs rank; families subsume them. Theaura-registryflat API (append/load/rank_by/optimize) stays regardless —optimizebacks the in-sample step of walk-forward and is library surface; only the CLI commands would go.Neither is clearly default (does
aura runwant a persistence side-effect, or stay a pure quick-check?), so this is a deliberate design pick, not a tidy.Context:
docs/design/INDEX.mdC18 realization note (cycle 0045) records this as a deferred follow-up.Minor sub-item (low, cosmetic)
Family-wrapped
aura sweep/mc/walkforwardstdout nests the report viaserde_json::json!(→ alphabetical manifest keys, leadingbroker) whileruns family/runs listprint viaRunReport::to_json()(declaration order, leadingcommit). Both valid JSON, round-trip unaffected (the storedfamilies.jsonluses declaration order viato_string). If display consistency is wanted, render the wrapper by embeddingreport.to_json()instead ofjson!.