Files
Aura/docs
Brummel d96af7e1a2 audit: cycle close risk-regime axis — drift-clean after the C20 ledger fix (#210)
Architect drift review (c9d962f..HEAD). What holds: the nominee key is the
3-tuple (strategy, window, regime) and no argmax over regime_ordinal exists, so
the ledger's kept-separate / compared-not-selected semantics is what the code
does; the C18 manifest stamp is honest (the characterization pin flipped from
asserting absence to requiring the exact resolved 3/2.0, a strengthening, and a
real two-regime e2e catches per-cell mis-resolution); no dead code (cell.regime
and regime_ordinal are both read after the runtime-binding slice), absent/empty
risk keeps content-id parity, and CampaignGeneralization.regime_ordinal is
serde-default so pre-feature records still parse.

Resolution:
- FIX (inline, this commit): the spec promised a C10 AND a C20 note; only C10
  landed. C20's enumerated structural-axis list (strategy/instrument/broker/
  window) was left silently incomplete — the risk regime is added as the fourth
  matrix axis, with a dated realization pointer to the C10 semantics.
- carry (documented descope): no std::risk descriptor in CAMPAIGN_SECTIONS —
  risk is a top-level array, not a slot-bearing section; no invariant broken.
- carry (filed #212): the persist re-run + campaign_cell_key omit the regime
  because CellRealization gained none; the architect verified this is a LOUD C1
  drift-alarm refusal for a non-default regime + persist_taps, not silent wrong
  data (#212 corrected accordingly).
- trivial: validate_campaign's regime-check comment corrected (it catches NaN,
  not all non-finite; +inf is unreachable via JSON).

Regression gate: full workspace suite green, clippy clean (no dedicated
regression script; the suite + lint are the gate). Spec and plan removed
(git rm) at cycle close per the project convention. No baseline moved.

refs #210
2026-07-06 15:05:21 +02:00
..