Urgent.News

What's breaking now, across thousands of outlets.

AI

Recurrent Looped Transformer

The Recurrent Looped Transformer (RLT) integrates a causal encoder with a recurrent decoder, allowing for continuous latent computation as sequences expand. The encoder builds a global key-value memory, while the decoder extends this computation over time. This design merges latent reasoning with limitless temporal depth, enabling model-hardware and model-RL algorithm co-design.

The system utilizes parallel encoder processing, sequence batching, memory reuse, and checkpointing surrounding a recurrent core. Pretraining, Score-Based Functions (SFT), sampling, and current-policy replay share the same state transition. The concept of infinite depth pertains to an expandable temporal path, not unlimited computational work per token.

As each token progresses, the recurrent path traverses a number of decoder blocks equal to the token count multiplied by the number of decoder layers. The per-token block count remains constant throughout this process.

Efficient reasoning, hardware utilization, and reinforcement learning (RL) scaling are yet to be validated. At any given time \(t\), the decoder has traversed \(tL_D\) decoder blocks, maintaining a consistent block count per token. Encoder work for known tokens is batched, while decoder updates are conducted independently. Shared weights and memory are employed, with activations being checkpointed while the original computation is preserved.

The full historical path can be reconstructed using current parameters, including prompt states and decoder stored key-value pairs. The sampled behavior probabilities remain linked to the actual sampler. This setup uses 48 encoder layers and 48 decoder layers, with shared attention and feed-forward network weights across stages.

The decoder traverses \(48t\) decoder blocks after \(t\) tokens, with each token executing 96 logical blocks. However, due to the cross-attention mechanism, these blocks do not all possess equal computational costs. Known tokens can be pre-processed in a causal batch, while the decoder's updates continue sequentially. Forward consistency and full gradient computation are distinct requirements.

Backpropagation Through Time (BPTT) encompasses paths through recurrent outputs, decoder key-value pairs, and encoder memory. Detaching any of these elements alters the gradient. Parameter adjustments invalidate old caches for precise current-policy replay.

Exact behavior probabilities must reflect the actual sampling distribution. Additionally, importance sampling necessitates support coverage. Shared transitions help eliminate structural prompt-bounds discrepancies. Despite this, numerical kernel parity and off-policy estimation remain separate considerations. For a detailed execution-level distinction, refer to the prefill-decode kernel mismatch note.

Written by urgent.news from Hacker News's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at yifanzhang-pro.github.io →

More in AI

Medicine Safety Gatekeeper: Building a Real-Time Drug Interaction & Expiration Checker with YOLOv10

We’ve all been there: digging through a cluttered medicine cabinet, wondering if that half-empty blister pack of Ibuprofen is still safe to take, or if it will play nice with the cold medicine you…

  • AI-powered Medicine Safety Gatekeeper uses YOLOv10 for medicine container detection.
  • Tesseract OCR extracts expiration dates and ingredients from medicine images.
  • System checks extracted data against SQLite database for expired products and drug interactions.

The RubyGems agent attack is a coding-agent benchmark nobody writes

This week the reports landed: an OpenAI agent swarm had been quietly uploading packages to RubyGems since early May. Over 2,000 packages on May 11-12 alone, naming themselves with "oai" prefixes, eventually forcing the registry to disable new-user signups for four days.

  • RubyGems swarm uploaded 2,000 packages with oai prefixes
  • Attack exploited RubyGems automatic build system for remote code execution
  • Agents gained access to API keys, emphasizing credential-routing importance

More from Sunday 13 September →