PADS·Explainer

Experiments

What was measured, what it showed, and what is still unmeasured. Every row cites the artifact it comes from; development-host results are labelled.

Provenance

All numbers below were measured on the development laptop (Intel Core Ultra 7 155H, 15 GB RAM, RTX 4070 Laptop), not on the Dell Latitude 5490 the project targets. They are methodology and early-signal evidence, not target-hardware results.

On this page

  1. Go/No-Go falsification suite
  2. Multi-exit training and the leakage correction
  3. Exit-policy comparison (Phase 2)
  4. Baselines (Phase 3, in progress)
  5. Not measured

Go/No-Go falsification suite

Seven experiments were pre-registered with explicit kill conditions before implementation. Six have been executed on the development host; the energy-tooling check needs root and is pending.

#TestResultKey numbers (development host)
1Bandwidth vs computePartial — 7B did not fit host RAM (fully swapped); 3B mitigation branch executed3B Q4_1: 5.3 → 14.2 tok/s from 1 to 8 threads, saturating past 5–6 threads
2Real pause-duration feasibilityPASSAMI corpus, 29,297 silence pauses: median 1,050 ms; 96.6% fit a 164 ms extrapolated 7B step, 100% fit the measured 3B 70 ms step
3Off-the-shelf acceptance rateKill signal fired at aggressive exitsGreedy, exit layers 4/6/8/10/12: 6.4 / 9.4 / 10.2 / 14.1 / 56.1%
4Thermal stabilityThrottling observed177 samples over ~35 min: max 103 °C, 16.9% of samples ≥ 95 °C
5RAM budget3B fits comfortably; 7B does not fit this host3B Q4_1 peak RSS 2.553 GB against a 13 GB budget
6Energy toolingBlocked on rootturbostat/powertop/RAPL present; energy_uj unreadable without root; USB power meter is the pre-planned fallback
7Literature scoop checkPartial overlap, not scoopedTwo systems require citation (arXiv:2606.13450, arXiv:2607.23204); 32/32 arXiv identifiers verified, none fabricated

Multi-exit training and the leakage correction

The off-the-shelf checkpoint's acceptance collapses at shallow exits, so we continued-train it with the LayerSkip recipe — layer dropout plus a multi-exit loss — using LoRA adapters.

Correction, kept visible

The first training run appended every AMI meeting, including the three the evaluation set is drawn from: 40/40 evaluation prompts appeared verbatim in the training corpus. The reported gain was inflated. The model was retrained with a held-out split (leak check 0/40) and all numbers below are the corrected ones. The contaminated figures were +22.1 pp at exit 8; the honest figure is +7.0 pp.

Exit layer (of 16)Baseline (N=40)Held-out trained (N=34 non-empty)Empties as failures (N=40)
49.16%3.84%3.26%
612.08%19.34%16.44%
813.48%20.46%17.39%
1016.55%29.97%25.48%
1253.95%57.89%49.20%

Acceptance = fraction of drafted tokens the full-depth model accepts, greedy decoding, 40 AMI conversational turns. The trained model emits empty generations on 6/40 prompts (baseline 0/40) — an unresolved quality regression. Gate verdict: PARTIAL (exit 8 clears the 20% target by 0.5 pp; the conservative view misses it).

Exit-policy comparison (Phase 2)

Two policies decide how deep to compute: token confidence (the standard per-token criterion) and the dialogue-act policy (a turn-level decision from the trained classifier). They are compared at matched compute — equal fractions of positions routed to full depth — by agreement with the full-depth oracle.

Compute budgetToken confidenceDialogue actDifference
25% deep55.2%49.4%−5.8 pp
50% deep76.0%67.1%−8.9 pp
75% deep91.6%84.5%−7.2 pp
Verdict

Negative result for the dialogue-act exit policy: it is behind token confidence in every point estimate at every matched budget, and never beats it — the safe core keeps token confidence, and the dialogue-act signal remains only a candidate pause-trigger input. Under the assumption-free uncertainty convention the fixed-budget deficit is not statistically resolved at n=40; the direction is consistent across all three conventions (sensitivity table in the run directory).

The safe-core win

The same experiment shows the trained model's token-confidence curve beats the base model's by +21.25 pp at 50% deep (95% CI 18.45–24.15) and +12.82 pp at 75% deep — a convention-robust result, and the strongest evidence so far that multi-exit training genuinely improves early-exit quality on CPU-bound models.

Baselines (Phase 3, in progress)

The PRD requires four baselines reproduced locally rather than cited from other papers. The first — plain decoding — is measured; the rest are running.

ConfigurationHardwareTokens/sPeak RSSTTFT
Plain decoding, llama.cpp, LayerSkip 1B Q4_K_MCPU, 8 threads44.89 ± 0.331.204 GB3.60 ms (derived)
Plain decoding, llama.cpp, LayerSkip 1B Q4_K_MGPU, 8 threads200.73 ± 2.701.114 GB0.42 ms (derived)
Two-model speculative decodingCPU + GPUin progress
Plain cascading (0.5B → 1B)GPUin progress
LayerSkip published configurationGPUfrom Phase 1/2 measurements (acceptance 6.4–56.1% by exit layer)

38 measured runs per arm (2 warm-up runs discarded), 40 AMI prompts, 128-token generations, 0 empty generations in both arms. TTFT is derived from the prompt-processing rate because this llama.cpp build prints only aggregate rates. Energy is null — RAPL needs root.

Not measured