lane-integrity-checklisted

# Lane Integrity Check The forward track record is the project's one uncopyable asset. Any change in the same postal district as the lanes gets this check on both sides. ## Why this exists (paid-for lessons) - **2026-06-11 (THE big find):** rebalance events recorded weights/trades but never rewrote `paper_positions` — recorded weights would have silently diverged from the NAV book at the first monthly rebalance. - **Config hash = segment identity:** reverting a lane YAML in place reproduces an old hash and corrupts segment contiguity. Rule changes roll FORWARD as a new config version, never revert bytes. - **2026-06-16:** seeded book lanes were marked-to-market but INVISIBLE on the track-record endpoint (hardcoded lane list) — an integrity property can hold in the DB and still lie on the surface. ## Invariants to verify 1. **Lane YAMLs byte-stable:** `git diff --stat -- data/*.yaml` shows NOTHING unless this change is an explicit, attended new-lane/new-version ship. `paper_portfolios.yaml`, `book_lanes.yaml`, `conservative_atr_lanes.yaml` each keep their existing content hash (hashes are printed in registry rows and `/api/pi/track-record` segments). 2. **No strategy change to an in-flight tracked lane — ever.** Changes ship as NEW pre-registered lanes with their own hash and inception (see seed-a-lane). Arming/retrofitting an overlay onto a live lane is forbidden (TRIAL-001 annotation). 3. **Registry untouched:** `GET /api/pi/registry` —