Files
Aura/Cargo.toml
T
Brummel 008692c043 feat(0094): content-addressed reproduction — aura reproduce <family-id> (iter 1)
Restore C18 reproducibility for generated (blueprint-sweep) runs (#158, acc 2):
a sweep's topology is stored once, content-addressed by the topology_hash the
manifest already carries, and `aura reproduce <family-id>` re-derives every
persisted member bit-identically (C1) from the stored blueprint.

- aura-registry: a dumb content-addressed bytes store — Registry::put_blueprint
  / get_blueprint / blueprints_dir over runs/blueprints/<hash>.json. No sha2 dep
  (caller owns the hash; reproduction's bit-identical compare is the integrity
  check); absent id -> Ok(None) (treat-as-empty, like load).
- aura-cli: run_blueprint_member extracted from blueprint_sweep_family's member
  closure (behaviour-preserving; keystone stays green) so the sweep AND reproduce
  re-run the identical reduce-mode path — bit-identity by construction. The store
  write hooks the sweep persist seam (one blueprint per family, shared topo).
  reproduce_family_in loads each member's blueprint by hash, reconstructs the
  point from the recorded params (point_from_params, inverse of zip_params, over
  the WRAPPED signal's param_space so the prefixed knob names match), re-runs, and
  compares metrics. `["reproduce", id]` dispatch arm; refuse-don't-guess on an
  unknown id / missing stored blueprint (exit 2), DIVERGED -> exit 1.

Dependency decision (per-case review, ratified): enabled serde_json
`float_roundtrip`. Stored member metrics round-trip through families.jsonl as
f64 JSON; the default parser can be 1 ULP off, which would make disk-loaded !=
recomputed and "bit-identical" (C1) physically impossible. The feature guarantees
exact f64 round-trip. Blast-radius clean (full workspace suite green); it serves
determinism, the invariant reproduction rests on. Canary:
f64_blueprint_param_survives_store_round_trip_bit_identically.

Two plan bugs caught + fixed by the implement loop and verified: reproduce's
param_space must come from the wrapped signal (prefixed names, the #167 lockstep),
and the family id is 0-indexed (live-0 / smacross-0, not -1).

Verified: full workspace suite green (51 suites); clippy -D warnings clean; and
the binary end-to-end — `aura sweep` (3 members, one shared stored blueprint) then
`aura reproduce live-0` (3/3 bit-identical incl the open-at-end member), unknown
id -> exit 2. acc 1 (graph introspect --content-id) + acc 3 (Tier-1 id stability)
land in iteration 2 (plan 0094b).

refs #158
2026-07-01 02:55:52 +02:00

37 lines
1.4 KiB
TOML

# aura — a "game engine for traders": a Rust framework + playground to author
# trading nodes, backtest them deterministically and in parallel, compose them
# fractally, and freeze a validated strategy into a standalone bot.
#
# Workspace split is driven by the cdylib hot-reload boundary: `aura-core` is the
# shared contract that BOTH the engine and every hot-reloadable signal/node
# cdylib link against. Add crates only when a boundary proves real.
[workspace]
resolver = "3"
members = [
"crates/aura-core",
"crates/aura-std",
"crates/aura-engine",
"crates/aura-analysis",
"crates/aura-composites",
"crates/aura-cli",
"crates/aura-ingest",
"crates/aura-registry",
]
[workspace.package]
edition = "2024"
version = "0.1.0"
license = "proprietary"
publish = false
[workspace.dependencies]
serde = { version = "1", features = ["derive"] }
# float_roundtrip is load-bearing for bit-identical reproduction (`aura reproduce`,
# #158): an f64 blueprint param (e.g. a Bias `scale`) is round-tripped through the
# content-addressed store as JSON, and the DEFAULT serde_json parser can be 1 ULP off,
# which would re-derive a member as DIVERGED. This feature guarantees the exact f64 is
# parsed back. Exercised (with a 1-ULP canary value) by aura-cli's
# `f64_blueprint_param_survives_store_round_trip_bit_identically`.
serde_json = { version = "1", features = ["float_roundtrip"] }