Methods › Natural Language Processing › Autoregressive Transformers › Universal Transformer
Universal Transformer
Introduced by Mostafa Dehghani et al. in Universal Transformers
archive 2025-07-28 Description, source and code snippet are the archive's method entry.
The Universal Transformer is a generalization of the Transformer architecture. Universal Transformers combine the parallelizability and global receptive field of feed-forward sequence models like the Transformer with the recurrent inductive bias of RNNs. They also utilise a dynamic per-position halting mechanism.
In Syntology repository known, no verified implementation (declared_code; repositories: 5 listed of 8 in the graph, strongest link: official). This answer is about arXiv:1807.03819, the paper the archive credits with this method.
Code Syntology holds under other names, as the lookup lists them (code_nearby); not a complete list, and none of them is this method.
- Agentic Transformer · shares_name_tokens (shares name tokens with this name; a different method) · level V3 · retrieve with
get_reference_implementation(name='Agentic Transformer') - universal technique · shares_name_tokens (shares name tokens with this name; a different method) · level V3 · retrieve with
get_reference_implementation(name='universal technique') - Waypoint Transformer · shares_name_tokens (shares name tokens with this name; a different method) · level V2 · retrieve with
get_reference_implementation(name='Waypoint Transformer') - Block-State Transformer · shares_name_tokens (shares name tokens with this name; a different method) · level V3 · retrieve with
get_reference_implementation(name='Block-State Transformer') - Bootstrapped Transformer · shares_name_tokens (shares name tokens with this name; a different method) · level V3 · retrieve with
get_reference_implementation(name='Bootstrapped Transformer') - A Universal Error Measure · shares_name_tokens (shares name tokens with this name; a different method) · level V3 · retrieve with
get_reference_implementation(name='A Universal Error Measure')
Origin paper of this answer, arXiv:1807.03819 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 17 ran (of which 8 constructed an object rather than computing a result; 17 with no instrument failure: 1 honoured, 0 violated, 16 with no contract checked; 0 where Syntology's instrument failed) · 8 unverified (of 25 harvested samples) · 24 pointer-only (licence). The instrument figure counts failures of Syntology's instrument, not of the code. Ran means executed on a synthesized input, not that the code is correct.
Syntology's have check for this name (free, it answers coverage only), read 2026-10-05; ask it again live. A level is the served verification level of that one answer; nothing here is summed across methods.
What each level means, quoted from Syntology's server card: V0 “imports”; V1 “executes against a synthesized fixture and returns a value of the recorded type”; V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)”; V3 “paper-derived property tests pass on both of those same two generations.” The card adds: “No rung on this ladder compares the served code against the authors' implementation, so treat every level as evidence about runnability and internal agreement, not about matching the paper's results.” A level quoted in two parts is one definition the card writes as two clauses joined by a double hyphen, each clause quoted on its own (how these levels are quoted).
Papers archive 2025-07-28
archive papers tagged: 18 · with a code link: 8 · where Syntology ran a sample: 4 (4 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran (4 of 18 tagged: 4 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument)
Page 1 of 1: papers 1 to 18 of 18, newest first by the archive's date (ties by slug), in archive order.
Repository counts are the archive's code-links table. A Syntology line states what Syntology ran from that paper's harvested code, as “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. It is per sample and not a correctness claim. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from.
-
PLUTO: Pathology-Universal Transformer 13 May 2024 · 0 repositories · arXiv:2405.07905
-
Investigating Recurrent Transformers with Dynamic Halt 1 Feb 2024 · 1 repository · arXiv:2402.00976
-
Self-Critical Alternate Learning based Semantic Broadcast Communication 3 Dec 2023 · 0 repositories · arXiv:2312.01423
-
Sparse Universal Transformer 11 Oct 2023 · 2 repositories · arXiv:2310.07096Syntology 3 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 1 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified (of 5 harvested samples)
-
UMMAFormer: A Universal Multimodal-adaptive Transformer Framework for Temporal Forgery Localization 28 Aug 2023 · 1 repository · arXiv:2308.14395
-
Beyond Universal Transformer: block reusing with adaptor in Transformer for automatic speech recognition 23 Mar 2023 · 0 repositories · arXiv:2303.13072
-
Semantic Communication with Memory 22 Mar 2023 · 0 repositories · arXiv:2303.12335
-
Towards Autoformalization of Mathematics and Code Correctness: Experiments with Elementary Proofs 5 Jan 2023 · 1 repository · arXiv:2301.02195Syntology official (archive's flag): 5 ran · 5 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified (of 7 harvested samples)
-
Universal Transformer Hawkes Process with Adaptive Recursive Iteration 29 Dec 2021 · 0 repositories · arXiv:2112.14479
-
The Devil is in the Detail: Simple Tricks Improve Systematic Generalization of Transformers 26 Aug 2021 · 2 repositories · arXiv:2108.12284Syntology official (archive's flag): 1 ran · 1 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified (of 2 harvested samples)
-
Using BERT Encoding and Sentence-Level Language Model for Sentence Ordering 24 Aug 2021 · 0 repositories · arXiv:2108.10986
-
Semantic Communication with Adaptive Universal Transformer 20 Aug 2021 · 0 repositories · arXiv:2108.09119
-
Automatically Ranked Russian Paraphrase Corpus for Text Generation 17 Jun 2020 · 0 repositories · arXiv:2006.09719
-
Universal Transforming Geometric Network 2 Aug 2019 · 1 repository · arXiv:1908.00723
-
Latent Universal Task-Specific BERT 16 May 2019 · 0 repositories · arXiv:1905.06638
-
Self-Attentive Model for Headline Generation 23 Jan 2019 · 0 repositories · arXiv:1901.07786
-
Attending to Mathematical Language with Transformers 5 Dec 2018 · 3 repositories · arXiv:1812.02825
-
Universal Transformers 10 Jul 2018 · 8 repositories · arXiv:1807.03819Syntology community repositories only · 17 ran (of which 8 constructed an object rather than computing a result; 17 with no instrument failure: 1 honoured, 0 violated, 16 with no contract checked; 0 where Syntology's instrument failed) · 8 unverified (of 25 harvested samples) · 24 pointer-only (licence)
Tasks archive 2025-07-28
20 shown of 43 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.
Usage over time archive 2025-07-28
Components: the archive holds no method-to-method composition, so PwC's Components table cannot be rebuilt; the Papers list carries no Results column for the same reason (the archive does not join its leaderboard rows to method tags).
Categories archive 2025-07-28
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections