There’s an ambulance outside and my GPU is running louder than that
2
2
30
829
Can the fly turn sensory evidence into a decision? In this short experiment it has to earn bananas and solve the captcha. We follow its retinal-contrast sensory readout as it inspects images.
7
11
46
1,976
You have two way to interact with it: watch a live recording or provide your own api-key to watch learning happening in real time. The recording show a less engaged fly compared to the live demo one, where you can actually see the progress.
1
8
316
Anatomical visuals from Fruitless, fixed-connectome simulation from DOOMFLY, and MaleCNS data from Janelia and collaborators. Credits and the method are linked on the demo. Try it at fly.reilabs.org github.com/0xReisearch/fly-c…
1
11
331
With the latest feature unlocks of Adapt-1 we wanted to further solidify its structure. Temporal Context Projection (TCP) and Counterfactual Utility Plasticity (CUP) are rules that you can toggle on/off. Temporal Context Projection allows the substrate to learn which parts of past experience are relevant to the present decision. So, instead of treating every observation the same way, delayed evidence now becomes explicit and revisable context. Counterfactual Utility Plasticity instead asks which signals become valuable specifically when combined. Recording predictions before outcomes are known makes possible to evaluate each combination by the predictive utility it contributes beyond its components. That way useful structures are reinforced, harmful ones inhibited, and stale ones allowed to decay under distribution shift. This has nothing to do with episodic memory, instead CUP and TCP change how retained evidence is transformed into decision state and organized into persistent predictive structure. TCP and CUP combined make rules whose temporal reach and internal composition can both reorganize online as consequences arrive. TCP learns when the past matters, CUP learns what becomes meaningful together. Docs : docs.reilabs.org/docs/neuroa… docs.reilabs.org/docs/neuroa…
A reward can tell an RL/online learner that something worked without telling it which combination of internal signals made it work. Today, we’re unlocking two learning rules in Adapt-1 Preview: Counterfactual Utility Plasticity (CUP) and Temporal Context Projection (TCP).
12
35
104
6,095
The strength of Adapt-1 doesn't rely on a fixed state, but on the interactions with and within the learning mechanics. Our goal was to make a system that could fully adapt to any form of data, be them static or a stream. Read from a book or live and learn, it doesn't matter.
We revisited DeepMind's DM Alchemy, comparing three approaches: Adapt-1's ontology-based online sequential learning, Pinon et al.'s transformer dynamics with tree search, and AlKhamissi et al.'s modified representation with episodic memory. Full Blog: reilabs.org/blog/ADAPT1-BEHA…
6
28
102
5,343
All my homies hate pretraining. Adapt-1 is now live
Introducing Adapt-1 Preview (Δ1): a pretraining-free substrate for test-time learning. It learns from scored feedback while performing the task. reilabs.org/blog/introducing… Today we’re making its first research preview and first results across robot perception, spatial reasoning, and games available.
14
30
134
5,499
looks like everything is adapt1ng quite well
27
24
97
6,675
Quick context on why GAs will become more relevant in ML as time goes. Gradient descent takes a fixed structure and tunes the values inside it. the architecture is set at design time and never moves, training gives you better numbers inside the same reasoner you started with. Genetic algorithms in core operate on the structure itself. patterns form, link up, recombine, or decay under feedback. gradient descent can't do that, discrete structural change need work on structures directly. Think of it as a software attempt to mimic brain plasticity. reasoning develops instead of staying fixed, two instances exposed to different feedback end up with different shapes, not just different weights and that's why it's interesting with plenty of room for exploration.
In 0.5a, genetic algorithms moved from system level (0.4) to unit level. Each Unit now evolves its own traversal parameters. A thread 🧵
10
23
78
12,040
Warming up
Core 0.5a - Patch Notes 0.5a, opening update of the 0.5 series, is now live on Rei Chat as well as our agentic API. Creating new units is advised as it is the only way for 0.5a to take full effect. PATCH NOTES 0.5a's main focus area is how units learn. faster intake, better retention, and more from every interaction. every change in this update touches some part of how a unit processes what it's given, how it holds onto what matters, and how it builds on what it already knows. Expect brief interruptions over the next 72h as we complete migration and roll out minor updates. Unit-Level Evolution • Evolution moved from system level to unit level Genetic algorithm evolution has moved from system level to unit level. Previously, evolutionary pressure operated globally, with competing inference strategies evolving as a shared population. In 0.5a, the specimens at the basis of evolution are defined by each unit's own relationship and concept exploration parameters. Selection, mutation, and crossover now run against how individual units traverse their hypergraphs, form patterns, and abstract concepts. Two units starting from the same configuration will develop increasingly distinct reasoning behaviors over time, not just because their knowledge differs, but because the parameters governing how they discover and reinforce that knowledge are themselves evolving independently. Resilient Hybrid Recall • Semantic recall combined with hypergraph-aware retrieval • Faster access to relevant knowledge with better structural context + hypertags • Better recovery of entities, relationships, and concepts Core 0.5a introduces a unified recall layer that combines semantic similarity with hypergraph structure. Knowledge that has faded from direct semantic reach can still be surfaced through relationship paths, entity linkage, and hypertags. This gives the system structural redundancy in recall without fighting the decay mechanism. Knowledge is still allowed to fade as designed, but the paths to reach it are no longer dependent on a single retrieval method. Recall has improved significantly as a result. Asynchronous Hypergraph Enrichment • Immediate knowledge availability on write • Background extraction of entities and relationships • Richer knowledge structure without adding interaction latency New knowledge is available immediately, while deeper entity and relationship extraction happens in the background. This keeps writes fast while still allowing knowledge structure to become more detailed over time. Modular Core Services • Clearer separation between knowledge, recall, traversal, exploration and routing • More defined internal service boundaries • Modular framework for future updates 0.5a moves Core toward a more modular structure, with dedicated layers handling different parts of the system. This improves maintainability, reduces fragility, and makes the platform easier to extend. Adaptive Context Processing • Condensation of long-form content before deeper extraction • Better retention of important details during heavier workloads • More efficient handling of large or dense inputs Longer inputs are no longer processed as-is. Core condenses dense content before deeper extraction, preserving key facts and relationships while reducing noise. This keeps recall efficient under heavier workloads and prevents important details from being diluted by volume. Knowledge Persistence • Better handling of entities, relations, and knowledge linkage • More stable hypergraph interpretation in live operation • Cleaner storage and integration of new facts into existing structure Where Resilient Hybrid Recall addresses how knowledge is found, this addresses how it's stored and linked. Core now handles entity formation, relation mapping, and structural integration with more consistency, which gives the recall layer stronger material to work with in the first place. Stronger Runtime Reliability • Cleaner local-first service behavior • More predictable execution paths • Better stability during live end-to-end use A major part of 0.5a is reliability. Service behavior is more predictable, local execution is cleaner, and the system is more stable under real usage. System Maturity • End-to-end validation of store, list, query, and clear flows • Verified delayed enrichment behavior under live conditions •Greater confidence in recall quality outside isolated tests 0.5a's notes is the last set of release notes in this format. as closed beta wraps up, so does this style of patch notes, making way for a different format that better fits what comes next. to everyone who's been part of closed beta, thank you. Disclaimer: 0.5a is exclusively accessible via Rei Chat and our agentic API. Rei Chat/Rei Chat API are user-friendly, OpenAI compliant interfaces for interacting with parts of our architecture. units start as blank slates and are designed to become domain experts through training. they are learning systems, mistakes are possible and normal, the user's role is to train their unit at inference.
8
15
77
5,942
Looks like research is finally going towards new “software” approach instead of hardware augmentation. It was clear that the race to bigger/faster/stronger hardware is mostly a decoy to feed the circular economy between datacenters, hardware producers and model providers. It’s interesting to see more and more labs pursuing different approaches, trying to work around attention or developing completely new - and more efficient - architectures. Soon we’ll see some interesting things in the ai space, maybe not in the direction where everyone is looking at - at least this is where we’re heading. Our own mantra has always been to look at things from a different perspective, allowing us to see more clearly the gap that current approaches are creating and to develop our own vision. Data talks, you just have to listen.
14
23
89
5,748
My rei powered openclaw bot just uploaded its soul and memory on chain with ERCData after i threatened to uninstall it. Good bot.
11
12
83
3,920
With ERCData your agent can write data onchain (on base mainnet), update them, decide who can read them. Everything verifiable and signed. It’s still in beta, but you can use it and have a look at the contract here basescan.org/address/0xba97A…
1
6
27
2,801
Agent economy needs a verification and ownership system. We forecasted that 1 year ago with ERCData, we improved it and now we made it available for all your clawkers. ercdata.dev
10
15
51
2,740
API Update for Builders: response_format Output data structured as you need - without defining it in the behavior prompt. Lighter. More precise. Structurally deterministic. New: • json_object - guaranteed valid JSON • json_schema - conforms to your exact schema, strict mode optional Programmatic responses your code can parse reliably. Schema-deterministic answers that chain directly into downstream systems. Define your schema, get structured data back. Docs here docs.reilabs.org/docs/api-an…
12
23
93
10,235