docs(handover): 5 spark-level anomalies — tripwire +$10.64 UPWARD drift, lev 3→2 clamp, over-entry guard live-confirmed, EXIT-mislabel live, bimodal 6s/12s cadence

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Codex
2026-07-13 17:37:05 +02:00
parent 6757356e6c
commit 1a28b3c14a

View File

@@ -87,6 +87,31 @@ journal lane auto-drains the spool or rows need manual JSONEachRow replay
11. **Missing venue truth**: dolphin_uv.exec_journal etc. fine; but relax-window 11. **Missing venue truth**: dolphin_uv.exec_journal etc. fine; but relax-window
trades need DO_NOT_ACCOUNT tags before parity ledger consumes them. trades need DO_NOT_ACCOUNT tags before parity ledger consumes them.
## ANOMALIES — "that's odd" caught at spark level (operator order: log before fire)
1. **E-TRIPWIRE capital anchor drift** — 17:20:21 CEST at DASH fill
(0c2ee114): expected 49,550.8744 vs observed 49,561.5166 = **+$10.64 (~2bps)**.
Promo metadata then anchored capital at the OBSERVED value. Likely fee/timing
accounting at fill, but capital = anchor + Σ deltas is sacred (zombie-trades
lesson) — reconcile which side is right before it compounds.
2. **Leverage clamp mystery** — promotion line said `lev=3 raw_conv=8.0`
(intent c16ae587), venue log line: `leverage SET symbol=DASH-USDT 1→→2`, and
the next intent journaled `leverage=2`. Something between bridge sizing and
venue SET clamps 3→2 (venue max for DASH-USDT? sizing bridge internal_lev
0.637?). Money-path arithmetic — verify deliberate, not silent.
3. **KERNEL_REJECTED over-entry, live confirmation** — 17:22:40 brain re-fired
DASHUSDT SHORT while slot 0 already held DASH short (13 bars). Pre-wire FSM
refusal (same-millisecond receipt, no HTTP). Guard WORKS; upstream
position-blindness (PRIME 2.7× over-entry finding) remains the disease.
4. **EXIT-mislabel parade confirmed live** — exec_journal writes an EXIT BRIDGE
row per no-entry scan (uv-trade-* ids, ~12s apart, no real exits). Known
cosmetic item, now confirmed polluting exec_journal volume/queries.
5. **Bar cadence is BIMODAL, not slow** — BAR pulse instrumentation (cc01d28)
shows consecutive scan numbers with dt ≈ 6s OR ≈ 12s (exact doubles), nothing
between. The "11.06s average" = ~6s base clock (matches NG7's 5.97 pin) with
frequent double-length beats. Cadence question is now: WHERE does UV lose
every other scan (NG7 emission jitter / HZ pickup / dedup gate)?
## DOCTRINE REMINDERS (cost blood today) ## DOCTRINE REMINDERS (cost blood today)
- Never edit vendored copies; sync-gate REFUSE = port UP + prove zero drift before - Never edit vendored copies; sync-gate REFUSE = port UP + prove zero drift before