Make upgrades manageable
Integrate a new specialist, tool or memory and directly test the existing behaviour it affects.
ERAIS / Efficient Routed Adaptive Inference System
ERAIS brings specialist components into one architecture. Native language training starts with raw bytes; Fracture brings in skills learned by existing models. We’re testing how language, vision, audio, reasoning and memory can work together.
Connect the relevant expertise, carry state forward and account for the work performed.
The goal is growing capability within a practical operating budget.
See what has runWhy it matters
Selective execution is a route to investigating lower operating costs and deploying useful capability across a wider range of hardware.
Integrate a new specialist, tool or memory and directly test the existing behaviour it affects.
Move capable systems from datacentres toward workstations, field equipment and edge devices.
Use measured access patterns and execution costs to identify what the architecture needs from the machine.
These goals connect the architecture to a commercial question: how much useful capability can a team develop and operate within its budget?
Get help with your AI projectModular development
Test an audio, vision or specialist addition as a separate candidate. Check when it should run and compare the existing language behaviour before and after the change.
A recorded integration experiment trained with real audio and labelled video while preserving the frozen language core and inactive capability exactly in the tested configuration. That gives us a concrete starting point for testing modular upgrades.
See how this was testedAdd a capability
Integrate a candidate specialistPreserve required behaviour
Compare against the retained referenceUnderstand a regression
Trace the change, inputs and outputsRecover a working system
Restore its recorded state and configurationExecution evidence
The current review covers retained connectome models, exact-state checks and runtime improvements. Earlier training and conversion records remain available below.
Engineering evidence · checked 2026-09-20
Source models, execution checks and component timings from the latest engineering review.
166,700 retained neurons
25,582,938 directed pairs
malecns-v1.0 is loaded in a running executor. The source import reports complete retention of its declared network.
Model dynamics, input mappings and anatomical coordinate coverage are specified separately.188,508 retained neurons
13,620,865 directed pairs
banc-888-v3 is loaded in a running executor. The source import reports complete retention of its declared network.
Model dynamics, input mappings and anatomical coordinate coverage are specified separately.30.3% lower CPU time
935.1 → 651.8 ms per 20 ms simulated interval in the recorded laptop comparison.
Same 200 physics steps per interval. Eight measured intervals per arm; shared-host component timing.6.2–7.1% lower CPU time
The narrow prefetch update improved both recorded laptop tapes. Complete mutable state and weights matched byte-for-byte.
Neural-kernel measurements with frozen and learning-enabled profiles. Whole-loop cost includes physics and other work.One shared-laptop ABBA comparison, eight measured intervals per arm, with retained physics cadence. Component timing.
Fixed retained-image tapes, eight measured intervals per variant. Complete state and weights compared byte-for-byte over four intervals. Neural component timing.
Actual simulator wiring, source identity, complete activity, image hashes and clean checkpoint/exit were checked.
ERAIS source: 6f20efa8bf6f6f2a86312d0fb80eef1460bb19a1. Each measurement retains its source receipt digest in the downloadable record.
A same-host developmental diagnostic, not a matched-quality control, paper reproduction, whole-system energy measurement, or model-superiority result.
Selected Gemma MLP execution measured 1.982× the speed of its previous implementation on 48 retained rows, with unchanged output for those rows.
Two cloud CPU configurations resumed the same retained 3M checkpoint and completed the same 27-update interval. The faster configuration measured 1.390163× the training throughput.
At TinyStories paper-text scale on the same CPU host, the corrected ERAIS full-stack window measured 3.40× the dense reference throughput and 68.45% lower CPU-package energy per reported valid target.
A cloud CPU continuation completed 16.79M valid targets with exact terminal state, sustained throughput, zero swap events, and high use of its declared thread budget.
The repaired TinyStories full stack completed 205 updates on a T4 with bounded quality movement, active cognitive paths, compact sparse execution, and an exact-resume checkpoint.
A governed T4 training intervention reduced peak accelerator memory by 45.13% while retaining more than 100,000 valid targets/s and terminal quality inside the registered window.
At 1.61B stored-parameter scale, a larger-batch A10G arm completed ten finite updates, exercised the full governed stack, retained exact restartability, and exposed GPU occupancy as the next optimisation target.
These completed tests give the programme a foundation. Integration and trained capability are qualified for each model profile.
The public demo connects measured Fracture, native-byte language, sparse vision and symbolic reasoning results without exposing the proprietary engine.
Explore the ERAIS demosNative training snapshot · published 4 September 2026
This completed adaptive raw-byte run used 87.3M parameters with sparse K1–2 routing active. It records one trained profile. Longer matched experiments test where quality and active-compute advantages emerge; their results are assessed separately.
Measure improvement on held-out tasks and a fixed evaluation chosen before the result.
Can routine input become less work without losing meaning, order or useful surprises?
Can stored capability grow while the work performed for one task stays under control?
Does any advantage remain against a conventional model under the same declared rules?
The commercial opportunity grows when a model can deliver the required result on a workstation, product or field device at an acceptable operating cost.
One architecture / many ways to work
ERAIS is being built to connect language, voice, vision, memory and action through shared state and explicit component interfaces.
Read procedures, compare evidence and prepare a decision without sending every task to a giant datacentre.
Hear a spoken note or an alarm, then bring in only the knowledge needed for that moment.
See an asset or defect, compare the relevant evidence and leave unrelated parts of the system idle.
Execution and evidence tools
The ERAIS Observatory keeps each result connected to what changed, what ran, what failed and what happened next.
That means less time reconstructing an experiment from scattered logs. A result can be explained, repeated, repaired or rejected from the record that produced it.
See how NeuroForge tests its own workKeep the accepted system still.
Record what actually ran.
Find the part that changed.
Keep, repair or restore.
Fracture / the migration bridge
Fracture brings learned capability into ERAIS execution, from converted speech and language components to complete supported game-control policies. It builds on knowledge already captured in existing models.
The 11 September runtime record describes native text attention and KV execution with full-K converted language MLPs, alongside the donor tokenizer, embeddings and multimodal wrapping. The API guide explains how discovery identifies the selected dense, hybrid Fracture or native profile and its limits. The recorded native cutover shares the World owner with the public API and Discord adapters; it does not establish signed Discord acceptance, assistant quality, sparse savings or paid readiness.
Story Lab uses a separately trained raw-byte language checkpoint. The Minecraft player has its own perception-and-action runtime.
Implementation, integration and trained capability are separate milestones. Each checkpoint uses a declared profile; reconstruction establishes an exactness baseline, and recovery and adaptive execution must earn their own quality and resource results.
Build the next cognitive architecture
We’re looking for research collaborators, model builders and investors who want to test the architecture on consequential tasks and develop its commercial applications.