MACRO: Markov Chain Routing of Transformer Layers¶
Core mechanism. The central operator runs locally. Private production data, large-model weights, and custom serving were not reproduced; paper and local results are separate.
Paper information¶
| Field | Details |
|---|---|
| Paper | arXiv 2608.05872 |
| Organization | Heinrich Heine University Düsseldorf |
| First public release | 2026-08-06 (arXiv v1) |
| Authors' code | Public implementation |
| Adapter / method | macro |
| Local reproduction code | src/auto_research/reproductions/macro/ |
Original paper¶
Motivation and method¶
Topic: dynamic layer routing. A fixed sequential pass through every Transformer layer is not always optimal. MACRO represents skips, repeats, and residual additions with a context-conditioned Markov policy. Feedback updates the routing distribution and top-k Viterbi decodes candidate programs without changing base-model weights.
Architecture¶
flowchart LR
N0["Task context"] --> N1
N1["Markov routing policy"] --> N2
N2["Skip, repeat, or add"] --> N3
N3["Top-k Viterbi"] --> N4
N4["Frozen LLM"]
Key figure from the paper¶
Figure 2: Overall workflow, stages, and data flow. From the original paper; copyright remains with the authors.
Core equation¶
\(p(\rho\mid x)=\prod_t\pi(a_t\mid \ell_t,b_t,d_t,x)\).
Paper results¶
Mean accuracy improves +5.0% over sequential execution and +7.2 points over Dr. LLM. Search time falls from 14.8 hours to 1.6 hours (9.4×).
Local reproduction¶
Search 81 skip/repeat/residual routes in a deterministic classification mini-suite. The operator is also an optional structure in micro-LLM evolve.
See the stable metrics; checkpoints are not committed.
Local comparison: The matched control disables the defining mechanism and uses the same splits and budget. The treatment uses
macro; relative results are inpublic-seed42.json. Cross-paper percentages are not applicable.
Reproduction boundaries¶
- The local result checks executable mechanisms and comparison direction, not paper scale.
- Private features, production traffic, and serving are unavailable. Original online numbers are references only.
- Executable evolve structures are registered as candidates. Serving-only methods stay standalone runnable adapters, not trainable genomes.
