✗ Mechanism failed 2026

Strongly Connected Sparse Routing

Implementation & benchmark of arXiv:2607.02754 — Possibilistic collapse and extremality of simplicial distributions

Usefulness6/10
Difficulty6/10
Novelty8/10

Source paper: Possibilistic collapse and extremality of simplicial distributions arXiv:2607.02754 ⓘ · analyzed Aug 30, 2026

AI-generated research hypothesis, automatically tested. Not peer-reviewed.

Idea description

Replace independent soft MoE router decisions with locally consistent categorical supports across overlapping token contexts, and bias the router toward supports that are strongly connected. A strongly connected support scenario cannot be reduced to a smaller nontrivial support while preserving local surjectivity, so the resulting routing distribution is encouraged to be an extremal point rather than a diffuse mixture of routing policies.

Formulas

$$q\preceq p\quad\Longleftrightarrow\quad \operatorname{supp}(q_x(e))\subseteq\operatorname{supp}(p_x(e))\quad\text{for every context }x\text{ and local assignment }e.$$
$$a=c_{0}\longleftrightarrow c_{1}\longleftrightarrow\cdots\longleftrightarrow c_{m}=b,$$
$$G\leq F,\quad G(c)=F(c)\text{ for some maximal }c,\quad F\text{ strongly connected}\ \Longrightarrow\ G=F.$$
$$\mathcal{L}_{\mathrm{SC}}(p)=\sum_{a,b\in C_{\max}}\max\!\left(0,\,\tau-\operatorname{Conn}(a,b;F_p)\right),\qquad F_p(c)=\{e:p_c(e)>\epsilon\}.$$

Mathematical statement

For a finite poset C of routing contexts, let F:C^op -> Set assign each context c a finite nonempty set F(c) of supported local assignments, with restriction maps F(c)->F(d) for inclusions d subset c. A subscenario G <= F means G(c) subseteq F(c) for every c, and G is non-trivial when every G(c) is nonempty and its restriction maps are surjective. Two contexts a,b are F-strongly connected when there is a zigzag a=c_0 <-> c_1 <-> ... <-> c_m=b such that every corresponding restriction map F(c_i)->F(c_{i+1}) is an isomorphism. Proposition 4.25 states that if F is strongly connected, G <= F is non-trivial, and G(c)=F(c) at one maximal context c, then G=F. The paper's extremality criterion applies this support condition to a possibilistic collapse: a probability distribution p is a vertex when its Boolean support scenario admits no proper nontrivial subscenario. We use the support preorder q <= p iff supp(q_c) subseteq supp(p_c), so support pruning corresponds to moving to a face of the routing polytope. Here C is a manually defined overlap poset of token windows, F(c) is the set of supported expert assignments for window c, and restriction maps delete experts associated with removed tokens.

Implementation notes

Integrate this into the MoE router immediately after router logits and before top-k dispatch. Use overlapping contexts such as token windows of length 2 or 4, consecutive microbatch groups, or the same token under two data augmentations. For each context c, compute router probabilities p_c over expert assignments; define the Boolean support F_p(c)={e:p_c(e)>epsilon}, with epsilon initially 1e-3 and optionally annealed downward. Build a bipartite incidence graph whose nodes are maximal contexts and supported assignments; connect contexts when their overlap restriction maps are bijections on the currently retained supports. Pseudocode: (1) logits z_c = router(h_c); (2) p_c=softmax(z_c/T); (3) retain edges e with p_c(e)>epsilon; (4) repeatedly remove an edge only if every restricted child context remains nonempty and every parent-to-child restriction remains surjective; (5) compute connected components among maximal contexts after keeping only bijective overlap links; (6) add lambda times the number of disconnected component pairs to the loss, or use a straight-through support mask; (7) renormalize p_c on retained experts and dispatch top-k. The paper supplies the exact support-order and connectivity certificate; the engineer estimates supports from probabilities and connectivity with union-find plus degree checks. First test Switch-Transformer or a 4-expert MLP-MoE on CIFAR-100 or a small C4 language subset, comparing standard top-2 routing at equal FLOPs. Success means lower router entropy and expert collapse, more balanced expert utilization, and equal-or-better validation loss with fewer active expert-token edges.

Verification

Mechanism failed

Stage 1 · Toy mechanism gate: Failed ✗

Stage 2 · Mechanism transferred to benchmark: Not tested

Stage 2 · Practical benchmark result: Not run

Methodology: Toy-system gate first; the benchmark stage runs only after a pass. How verification works

Stage 1 — Mechanism check agent confidence 8/10

Built a four-expert top-2 MoE prototype with a finite-set strong-connectivity sanity check, consistency/entropy router regularization, support diagnostics, and epsilon pruning. The proposition check passed, and the regularized model improved accuracy (0.6729 vs 0.6274), loss (0.6128 vs 0.6400), and utilization imbalance (0.1062 vs 0.1282) in one fixed run. However, epsilon=1e-3 retained all four experts for both methods and top-2 dispatch still used exactly 2 edges per token, so the claimed strongly connected sparse-routing effect was not demonstrated.

Agent confidence
8/10
Baseline
loss=0.64005, accuracy=0.62744, router entropy=1.11691, utilization imbalance=0.12817, mean support at epsilon=0.001=4.0, dispatch edges/token=2.0
Idea
loss=0.61276, accuracy=0.67285, router entropy=1.11471, utilization imbalance=0.10620, mean support at epsilon=0.001=4.0, dispatch edges/token=2.0; evaluated pruning epsilon=0.12 but top-2 remained 2 edges/token

Limitations: Only one tiny synthetic binary-classification run and one fixed seed were tested. The categorical restriction maps were instantiated as identity maps rather than a full overlapping-window assignment construction; no CIFAR/C4 benchmark, FLOP accounting, multi-seed confidence interval, or true variable-k sparse dispatch was tested.

How to run: python3 sc_routing_experiment.py

Verdict computed by deterministic test code from paired-seed statistics — not by the language model.

Artifacts

Implementation overview ⬇ Download all as ZIP 4 files · code, reports and structured results