Ship the session-breakout demo as a World-consumable Composite blueprint #94

Closed
opened 2026-06-17 18:53:03 +02:00 by Brummel · 0 comments
Owner

Surfaced by the GER40 research deep-dive fieldtest (docs/specs/fieldtest-research-breakout-deepdive.md).

The flagship real-data demo (commit 5b5f034,
crates/aura-ingest/examples/ger40_breakout_real.rs +
examples/shared/breakout_real.rs) ships the session-breakout as a
hand-wired raw FlatGraph built by Harness::bootstrap. But every World
orchestration family — sweep, walk_forward, optimize — consumes a
Composite blueprint (it needs param_space() + bootstrap_with_cells). A
FlatGraph has no param space.

So to take this exact strategy into the World, a researcher must first
re-author all 13 nodes + 14 edges + 4 roles as a Composite by hand. The
fieldtest did exactly this and the re-authored Composite reproduced the shipped
FlatGraph's numbers EXACTLY (entry=3,exit=5 → −45.0; 2024 → +203.4 / 62
sessions) — strong evidence the only gap is the form, not the behaviour
(C23 behaviour-preserving holds).

C20/C21 promise a strategy blueprint is "reused across backtest, sweep, visual
workspaces", and the milestone fixtures demonstrate this for SMA-cross — but the
just-shipped real-data flagship ships in a form the World cannot consume, and
the ledger does not say which form a shippable strategy should take. A
consumer cannot tell from the public surface whether the FlatGraph form is
intentional or a gap.

Recommend: ship the breakout as a reusable Composite blueprint (the
authoring form; FlatGraph is its compiled target per C11/C23), so the demo's
strategy is World-ready — single backtest, sweep, walk-forward and
multi-instrument compare all bootstrap from the one blueprint. This is the
highest-value follow-up: it converts the deep-dive's #1 friction into
capability and dogfoods the blueprint path on real data. Couples with the
period-coupling fix (sibling issue) — the blueprint is where the period becomes
a single coupled knob.

**Surfaced by the GER40 research deep-dive fieldtest** (`docs/specs/fieldtest-research-breakout-deepdive.md`). The flagship real-data demo (commit `5b5f034`, `crates/aura-ingest/examples/ger40_breakout_real.rs` + `examples/shared/breakout_real.rs`) ships the session-breakout as a **hand-wired raw `FlatGraph`** built by `Harness::bootstrap`. But every World orchestration family — `sweep`, `walk_forward`, `optimize` — consumes a `Composite` blueprint (it needs `param_space()` + `bootstrap_with_cells`). A `FlatGraph` has no param space. So to take *this exact strategy* into the World, a researcher must first re-author all 13 nodes + 14 edges + 4 roles as a `Composite` by hand. The fieldtest did exactly this and the re-authored Composite reproduced the shipped FlatGraph's numbers EXACTLY (`entry=3,exit=5` → −45.0; 2024 → +203.4 / 62 sessions) — strong evidence the only gap is the *form*, not the behaviour (C23 behaviour-preserving holds). C20/C21 promise a strategy blueprint is "reused across backtest, sweep, visual workspaces", and the milestone fixtures demonstrate this for SMA-cross — but the just-shipped real-data flagship ships in a form the World cannot consume, and the ledger does not say which form a *shippable* strategy should take. A consumer cannot tell from the public surface whether the FlatGraph form is intentional or a gap. **Recommend:** ship the breakout as a reusable `Composite` blueprint (the authoring form; FlatGraph is its compiled target per C11/C23), so the demo's strategy is World-ready — single backtest, sweep, walk-forward and multi-instrument compare all bootstrap from the one blueprint. This is the highest-value follow-up: it converts the deep-dive's #1 friction into capability and dogfoods the blueprint path on real data. Couples with the period-coupling fix (sibling issue) — the blueprint is where the period becomes a single coupled knob.
Brummel added the feature label 2026-06-17 18:53:03 +02:00
Brummel added this to the GER40 breakout as a World-consumable Composite blueprint milestone 2026-06-17 18:57:43 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Brummel/Aura#94