Centralize runnable GER40 examples through instrument_spec (deferred from #22) #98

New Issue

2026-06-18T18:57:27+02:00

Brummel commented

2026-06-18 18:57:27 +02:00

Deferred from #22 (per-instrument pip). The CLI aura run --real path now sources
pip from aura_ingest::instrument_spec(symbol) (a typed vetted lookup). The runnable
GER40 examples still bake a const PIP_SIZE = 1.0 literal.

This is a consistency cleanup, not a bug fix: GER40/FRA40 quote in index points,
so 1.0 is the correct pip — the examples are honest today, just not routed through
the central metadata channel.

Centralize them: give ger40_breakout_blueprint a pip_size parameter (it bakes
SimBroker::builder(PIP_SIZE) at breakout_real.rs:252), source build_harness and
ger40_breakout_compare pip from instrument_spec, drop const PIP_SIZE. The
blueprint signature change propagates to ~14 call sites across 6 files —
examples/{ger40_breakout_real,sweep,walkforward,compare}.rs and
tests/{ger40_breakout_blueprint,ger40_breakout_world}.rs (the last has a
broker: "sim-optimal(pip_size=1)" pin at :64). All GER40/FRA40 callers pass the
looked-up 1.0, so the change is value-identical and behaviour-preserving (gated
determinism + blueprint param-space tests stay green).

depends on: #22 (instrument_spec / InstrumentSpec land there)
context: split out so #22 ships the actual CLI-path bug fix without an example-wide
signature refactor; spec-skeptic round-2 flagged the examples as a separable scope.

Deferred from #22 (per-instrument pip). The CLI `aura run --real` path now sources pip from `aura_ingest::instrument_spec(symbol)` (a typed vetted lookup). The runnable GER40 examples still bake a `const PIP_SIZE = 1.0` literal. This is a **consistency cleanup, not a bug fix**: GER40/FRA40 quote in index points, so `1.0` is the *correct* pip — the examples are honest today, just not routed through the central metadata channel. Centralize them: give `ger40_breakout_blueprint` a `pip_size` parameter (it bakes `SimBroker::builder(PIP_SIZE)` at breakout_real.rs:252), source `build_harness` and `ger40_breakout_compare` pip from `instrument_spec`, drop `const PIP_SIZE`. The blueprint signature change propagates to ~14 call sites across 6 files — examples/{ger40_breakout_real,sweep,walkforward,compare}.rs and tests/{ger40_breakout_blueprint,ger40_breakout_world}.rs (the last has a `broker: "sim-optimal(pip_size=1)"` pin at :64). All GER40/FRA40 callers pass the looked-up `1.0`, so the change is value-identical and behaviour-preserving (gated determinism + blueprint param-space tests stay green). depends on: #22 (instrument_spec / InstrumentSpec land there) context: split out so #22 ships the actual CLI-path bug fix without an example-wide signature refactor; spec-skeptic round-2 flagged the examples as a separable scope.

Brummel added the idea label 2026-06-18 18:57:27 +02:00

Brummel referenced this issue

2026-06-18 19:41:36 +02:00

SimBroker pip value is a global constructor literal, not per-asset #22

Brummel referenced this issue from a commit

2026-06-18 21:18:34 +02:00

feat: per-instrument pip metadata channel for the sim-optimal broker

Brummel referenced this issue from a commit

2026-06-18 21:18:34 +02:00

chore: cycle 0054 close — per-instrument pip; C10/C15 realization note, retire spec+plan

Brummel referenced this issue from a commit

2026-06-22 11:20:23 +02:00