Back to corpus
proposalexperiment writeup candidatescore 40

AGP Execution Roadmap V1

- `Gemma 4 E2B` Thunder stage-one LoRA backbone - full train and held-out route oracle artifacts - route/vitality head `v1` on original conservative labels - calibrated threshold sweep over saved oracle metrics - recalibrated route/vitality head `v2` - three-head controller with earliest-layer supervision - corrected `transfer_v2` same-host adapter run

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

- `Gemma 4 E2B` Thunder stage-one LoRA backbone - full train and held-out route oracle artifacts - route/vitality head `v1` on original conservative labels - calibrated threshold sweep over saved oracle metrics - recalibrated route/vitality head `v2` - three-head controller with earliest-layer supervision - corrected `transfer_v2` same-host adapter run - calibrated label regime: `kl=4.0`, `margin_delta=0.15` - held-out route accuracy: `0.8444` - held-out vitality accuracy: `1.0` - exact held-out separation for: - `accept_local` - `revive_local` - `escalate` - remaining route confusion is mainly: - `continue_local -> accept_local` This means the backbone hidden states are already useful enough to support a learned controller. The remaining work is to convert that controller into a real distributed latent-transfer system. - corrected dataset: `transfer_v2_k4_m015` - best run: `transfer_adapter_v2_20260418_000114` - best checkpoint: step `1400` - held-out overall: - cosine `0.9226` - MSE `0.1097` - held-out by route: - `escalate`: cosine `0.9310`, MSE `0.0792` - `continue_local`: cosine `0.9432`, MSE `0.0979` - `accept_local`: cosine `0.6189`, MSE `0.6541` - held-out by layer: - layer `30`: cosine `0.9360`, MSE `0.0868` - layer `26`: cosine `0.6189`, MSE `0.6541` - late-boundary transfer is already strong enough to justify the next routed-resume stage - true early-layer transfer is still weak - the next phase should not pretend these are the same problem

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.