Navigate

Quick find

Find what you need

Esc

Latest engineering review · 2026-09-20

The work, measured.

See which systems are running, what the latest checks established and where the engineering is going next.

Engineering evidence · checked 2026-09-20

Current systems and measured improvements.

Source models, execution checks and component timings from the latest engineering review.

MaleCNS source model

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.

Female BANC source model

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.

Articulated-body execution

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.

Native neuronal execution

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.
Methods, provenance and remaining 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.

  • Whole-CNS articulated simulation remains below real time on the measured laptop.
  • Calibrated muscle and CNS proprioception mappings remain research work.
  • Receptor-state images have incomplete spatial support.
  • Model quality and end-to-end commercial savings require workload-specific comparisons.

ERAIS source: 6f20efa8bf6f6f2a86312d0fb80eef1460bb19a1. Each measurement retains its source receipt digest in the downloadable record.

Download the current evidence record

Products, records and research

Find the detail you need.

Start a project

Work with NeuroForge.

Explore the Discord pilot, discuss a supported model conversion or define a research project around your workload and hardware.

Products and projects

Inspect the results

Inspect earlier experiments.

7 retained systems records through 2026-09-05 cover training, memory and execution. Their original environments and dates remain attached.

Open the recorded results

Follow the research

Put the next question to a test.

The next research question is whether richer cognition and greater stored capability improve useful quality while the active path stays constrained.

Explore the native programme

Each product page states its current availability. Each technical result states the model, task and conditions tested.

Open the detail you need

The record behind each decision.

Earlier systems results7 records · through 2026-09-05

Latest systems receipts through 2026-09-05

7 recorded systems experiments.

Local CPU, cloud CPU, T4 and A10G results retain their source versions, measured workloads and limitations.

3.40×descriptive same-host throughput ratio
68.45% lessCPU-package energy per reported valid target

A same-host developmental diagnostic, not a matched-quality control, paper reproduction, whole-system energy measurement, or model-superiority result.

Fracture component: less execution overheadSingle-thread CPU · 48 retained component input rows

earlier component comparison / no quality promotion

Selected Gemma MLP execution measured 1.982× the speed of its previous implementation on 48 retained rows, with unchanged output for those rows.

component speed ratio
1.982×
median component time
96.869 → 48.874 ms
retained rows checked
48

Boundary: An earlier covered-bank component configuration, compared with its previous implementation rather than a dense-model baseline. It does not establish complete-bank quality, end-to-end generation speed, held-out quality, or current serving savings.

ERAIS receipt · ab5cf5bd39 · 366110742bb7…

Cloud CPU choice: a faster exact continuationAWS CPU hosts · different processor families and thread budgets

paired short hardware comparison

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.

hardware throughput ratio
1.390163×
same 27-update interval
192.902 → 138.762 s
updates in each measured interval
27

Boundary: This compares hardware, physical-core allocation and thread budget, not ERAIS architecture efficiency. One short training interval does not establish sustained full-run speed, energy savings, finished training, or model quality.

ERAIS receipt · ab5cf5bd39 · 366110742bb7…

Local CPU: a clear small-scale systems signalFour-thread development CPU · FP32 complete training updates

descriptive diagnostic

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.

dense valid targets/s
1,971
ERAIS valid targets/s
6,698
CPU-package J/1K valid targets
14.53 → 4.58

Boundary: A same-host developmental diagnostic, not a matched-quality control, paper reproduction, whole-system energy measurement, or model-superiority result.

ERAIS receipt · e9d4068464 · 0aa8595157e2…

Cloud CPU: sustained full-stack continuationAWS c7i.4xlarge · eight assigned training threads

authenticated complete segment

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.

median valid targets/s
21,401
completed optimizer updates
4,100
assigned CPU-thread budget used
93.75%

Boundary: An authenticated bounded CPU continuation. It does not establish calibrated cloud energy, reconciled billing, useful generation, accelerator superiority, or production readiness.

ERAIS receipt · 5d526e4e53 · 8a77b33856c4…

Cloud GPU: full-stack execution at higher throughputSingle NVIDIA T4 · full-stack mechanics gate

operator-authenticated mechanics pass

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.

median valid targets/s
134,954
valid targets completed
33.59M
peak / total VRAM in GiB
11.4 / 15

Boundary: A single-worker T4 mechanics and resource result. It does not establish useful learning, total-system energy, dense superiority, multi-GPU scaling, or production readiness.

ERAIS receipt · d5c2794a65 · 311d52be34cb…

Cloud GPU: materially more memory headroomSingle NVIDIA T4 · governed exact-source training intervention

governed bounded training result

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.

peak accelerator memory
11,695 → 6,417 MiB
peak-memory reduction
45.13%
median valid targets/s retained
103,199

Boundary: One exact-source T4 training window. It does not establish a larger-batch or long-learning result, energy benefit, dense or inference superiority, multi-GPU scaling, or production readiness.

ERAIS receipt · da89d1bdb0 · eb5cb1dcd03a…

Stored scale: feasibility, headroom, and the next bottleneckSingle NVIDIA A10G · 1.61B stored-parameter graph

authenticated bounded systems pass

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.

median valid targets/s
6,491
mean / peak sampled GPU utilisation
20.61% / 97%
physical VRAM reserve
4.4 GiB

Boundary: A ten-update systems result at stored-parameter scale. It does not establish useful generation, equal-token learning improvement, distributed scaling, end-to-end energy, or commercial readiness.

ERAIS receipt · 47b9e613b9 · 576aa658e07b…

Current decision mapTechnical maturity, commercial availability and the next evidence test

Decision map

Now. Next decisive test. Held.

A compact view of the public programme. Every item separates technical maturity from commercial availability and names the evidence needed to move.

Now

Bounded work or evidence that can be inspected today.

3 items
NowCurrent public state

commercial

Four bounded engagement routes

Four scoped routes can enter qualification now: 10-Day AI Fit Test, Private AI Deployment Sprint, AI Evidence & Release Audit, Research & Benchmark Partnership.

Technical maturity
Operationally scoped
Commercial availability
Qualification open

Evidence boundary

NeuroForge is pre-revenue and has not completed an external pilot. Every route starts with written scope, evidence requirements and stop conditions.

Evidence exit

Accept the first qualifying engagement only when scope, data access, evidence and owner conditions are explicit.

NowCurrent public state

research

Native cognition: end-to-end byte learning

Two governed native-byte arms completed 262,400 updates and 536.3M valid byte-level targets each on the same bounded four-thread CPU envelope. The richer cognitive stack learned materially differently, but the fixed evaluation panel did not support a quality promotion.

Technical maturity
Mechanism demonstrated
Commercial availability
Research only

Evidence boundary

The native-byte mechanism and exact restart path passed, but the preregistered fixed quality panel did not promote a quality advantage.

Evidence exit

Test whether the richer learning trajectory transfers to qualified fixed holdouts, then compare stored-capacity and active-path matched dense controls under repeated independent evaluation.

NowCurrent public state

research

7 reviewed systems receipts

The current public state contains 7 source-pinned systems receipts and 6 architecture milestones spanning bounded local CPU, cloud CPU, T4 and A10G observations.

Technical maturity
Bounded systems evidence
Commercial availability
Research only

Evidence boundary

These receipts establish observed execution and resource behaviour in named runs. They do not establish matched-quality superiority, universal scaling or a production service envelope.

Evidence exit

Repeat the decisive native comparisons under matched quality, resource accounting and independent evaluation before promoting comparative claims.

Next decisive test

The nearest experiment or operating gate that can materially change the decision.

1 item
Next decisive testCurrent public state

research

Resolve native transfer and stored-capacity scaling

The next research question is whether richer cognition and greater stored capability improve useful quality while the active path stays constrained.

Technical maturity
Registered research programme
Commercial availability
Not commercially available

Evidence boundary

Schedule, representation and geometry results remain experimental until fixed holdouts, fair controls and resource accounting agree.

Evidence exit

Complete qualified fixed-holdout, stored-capacity-matched and active-path-matched comparisons with repeated independent evaluation.

Held

Claims and surfaces deliberately withheld until their own gates close.

2 items
HeldCurrent public state

governance

Legacy chat workspace remains held

The /chat/ workspace and /api/chat gateway need their own reviewed backend, access controls, monitoring and model labelling before a protected workspace pilot.

Technical maturity
Workspace backend not qualified
Commercial availability
Unavailable

Evidence boundary

This hold applies to /chat/ and /api/chat only. The public /v1 native text preview and Unified World follow their own live availability and capability contracts.

Evidence exit

Qualify the protected workspace backend, identity, retention, security, monitoring, rollback and capacity controls.

HeldNot promoted

research

Broad quality or efficiency superiority

No universal quality, speed, cost, energy or production-superiority claim is promoted from the current native or systems results.

Technical maturity
Comparative proof incomplete
Commercial availability
Claim held

Evidence boundary

Mechanism evidence and source-pinned receipts remain public with their scope; promotion waits for fair, repeated, matched-quality comparisons.

Evidence exit

Reconcile qualified dense controls, fixed holdouts and full resource accounting under an approved claim review.

Commercial qualification4 engagement routes · scope, gates and duration

Commercial availability

4 technical engagement options.

10-Day AI Fit Test (A$4,800 ex GST) tests a defined workflow. Deployment, evidence review and research projects have their own scope and acceptance requirements. Fracture and Discord enquiries start on their product pages.

AvailabilityAvailable as a bounded service
Exit / boundary

One repeated non-safety-authoritative workflow, one decision owner, an approved target or reference host, three to ten lawful non-sensitive cases, clear data/network/output limits, and a buyer review inside the delivery window are required before work starts.

Typical bounded durationUp to 10 business days
AvailabilityAvailable as a bounded service
Exit / boundary

A signed statement of work, approved data/model rights, representative frozen inputs, target environment, and acceptance owner are required before work starts.

Typical bounded duration2–4 weeks
AvailabilityAvailable as a bounded service
Exit / boundary

The release must be identifiable and the customer must lawfully provide enough artifacts, decision history, and reviewer access to reconstruct it.

Typical bounded duration2–4 weeks
AvailabilityProject by agreement
Exit / boundary

Named industry and method owners, lawful rights, a frozen baseline and holdout, negative-result protection, compute funding, IP/publication terms, and independent review must be agreed.

Typical bounded duration6–12 weeks
Design-partner qualificationMissing evidence and delivery gates for each candidate

Design-partner boundary

Implementation exists; external operation is gated.

Discovery is permitted. Delivery or co-development starts only after the named pre-contract evidence closes.

AvailabilityGated design partner
Missing gate

Exact-candidate external security and denied-path closure Representative load, admission, and at least 24-hour soak evidence Partner-environment restart, restore, rollback, and independent-operator completion

Duration after gate6–10 weeks after gate
AvailabilityGated design partner
Missing gate

Full 14-stage fresh-workstation execution Second-operator completion with founder interventions measured End-to-end artifact portability and customer-operability evidence

Duration after gate8–16 weeks after gate
AvailabilityGated design partner
Missing gate

A real manual external audit or equivalent repeated workflow A minimum cross-customer schema proved against the bounded use case Second-reviewer completion and repeatability evidence

Duration after gate6–10 weeks after gate
Historical evidence assemblyReviewed 2026-07-28 · retained failures and release boundary

Historical public-evidence assembly · reviewed 2026-07-28

The July handoff retained 41/41 canonical integrity and 38/41 raw discovery.

This is a historical release-candidate record. It remains inspectable without being mistaken for the date or state of the current native and systems programme.

Historical release hold

The July sanitised handoff passed canonical integrity, but the release remained held because active phase-discovery validation failed during assembly.

Canonical integrity
41/41
Raw discovery
38/41
Retained failures
3

Boundary: This is a historical release-candidate record, not the date of the current systems programme and not a public release authority.

Inspect the 3 retained validation failures
  1. Phase 27 · public metrics assembly

    Active validation failed.

    Exit: Close or explicitly retain the named validation failure in a newly assembled exact-SHA evidence release.

  2. Phase 28 · external evidence and benchmark contamination controls

    Active validation failed.

    Exit: Close or explicitly retain the named validation failure in a newly assembled exact-SHA evidence release.

  3. Phase 31 · full open dataset streaming ingestion

    Active validation failed.

    Exit: Close or explicitly retain the named validation failure in a newly assembled exact-SHA evidence release.

Historical claim reconciliationDetailed wording and terminal matrix retain separate source dates

Historical claim reconciliation · 2026-07-12

Detailed claim wording and the held terminal matrix keep their own review date.

The terminal handoff reconciles 44 claim rows and 99 evidence links with 0 recorded reconciliation issues. It remains historical: newer systems receipts do not prove or promote those claims.

Evidence maturity: Validated2validated
Evidence maturity: Provisional8provisional
Evidence maturity: Candidate15candidate
Evidence maturity: Unproven7unproven
Evidence maturity: Blocked12blocked
Source dates and authorityFour distinct clocks, company stage and the exact source pins

Four bounded engagement routes can enter qualification now. The current native programme has two completed long training arms and is testing whether richer cognition transfers under fair controls. Latest systems receipts run through 2026-09-05; the July detailed-claim and evidence-assembly records remain historical where marked.

Incorporated / founder-led / pre-revenueHistorical evidence assembly heldLegacy workspace held