Skip to main content

Vinh M3-V15 路 D-026 + G10 reproducibility

LIPS 4-axis evaluation harness.

Latency + Integrity + Physics + Skill 4-axis ablation across the four canonical configurations of the APEX stack. The hard-projection composition (V2 cvxpylayers per D-050 byte-equality lock) is the load-bearing claim; zero-shot Granite TTM is published as honest disclosure per D-052 G4 pivot rather than as the production forecaster path.

Engine: lips-v15-canned-fallbackDataset: FastF1 Hamilton 2024 Bahrain Q laps 4-5 holdout (canned)Seed: 42
ConfigurationLap-time MAE (s)Physics-violation rateGuardian approve %Inference latency (ms)
Zero-shot TTM (no projection)35.1842.0%0%484
Soft-loss-only (no projection)28.6618.0%12%504
APEX hard projection (V2 cvxpylayers)18.420.0%88%1030
Full 3-track ensemble + 8-tier physics17.610.0%94%1318

Swap-point: Vinh M3-V15 -> eval/Dockerfile + apex-bench/ (D-026 + G10 reproducibility statement)

What you are looking at.

The 4 rows map to the canonical ablation in paper 搂4.6 Reproducibility + 搂4.2 baselines. Row 1 (zero-shot TTM) is the G4 honest-disclosure baseline per D-052. Row 2 (soft-loss-only) demonstrates that constraint violation is hard to reduce via differentiable loss alone. Row 3 (APEX hard projection) shows the V2 cvxpylayers projection eliminating violations. Row 4 (full 3-track + 8-tier) is the production composition under D-010 + D-012 + D-015. Engine-agnostic byte-equality per D-050 applies between V1 NumPy + V2 cvxpylayers projectors (.to_text() output byte-identical modulo ENGINE line).

APEX-Bench v0.1.0 community leaderboard

Publish your own ablation. Open contribution surface.

Reproduce the four LIPS axes (lap-time MAE + physics violation + Guardian approve + inference latency) on your own forecaster + projector composition + submit. HEAD persists submissions in browser localStorage; community-wide leaderboard backend lands behind the {POST,GET} /api/lips-harness/{submit,leaderboard} swap-points. Every text field passes through the canonical regulatory-anchor scrubber before persistence per HARD-COMPLIANCE.

Top 0 submissions by lap-time MAE

Swap-point: Submissions persist in browser localStorage at HEAD; community-wide POST /api/lips-harness/submit + GET /api/lips-harness/leaderboard backend deploys per the M3-V15 swap-point