Work in progress · next generation

Verse 3

A bigger, harder, completely from-scratch language-model build. The target is roughly 7 billion parameters, with FSDP making multi-GPU training practical.

WORKING ON VERSE 3
From-scratch language model
VERSE 3
The next generation of the Verse series. Same core philosophy. Much larger scale. No final benchmark is claimed until it is actually measured.
~7Btarget params
FSDPtraining system
140Btarget tokens
~9*perplexity target
01 · The idea

The next jump
is not small.

01

From scratch

No API wrapper and no simple fine-tune. Verse 3 keeps the from-scratch philosophy: understand the architecture, training system and failure modes by building them.

02

~7B parameters

The architecture will be scaled by validating layers, model width, heads and FFN dimensions rather than blindly copying a reference configuration.

03

FSDP

Parameters, gradients and optimizer state are planned to be sharded across GPUs so the full model does not need to be replicated on every device.

02 · Architecture

Same DNA.
More scale.

Verse 3 stays in the same architectural family as the existing model: decoder-only Transformer, RoPE, RMSNorm and SwiGLU. The major change is scale plus the training infrastructure needed to support it.

CORE

RoPE

Rotary positional embeddings.

NORM

RMSNorm

Normalization stays familiar.

FFN

SwiGLU

Feed-forward capacity scales with the model.

03 · Training

140 billion
tokens.

7,000,000,000 params × ~20 tokens / param
≈ 140,000,000,000 training tokens

The plan is to scale the existing FineWeb-Edu pipeline. At this size, storage and throughput become real engineering constraints; disk capacity and hardware will be checked before a large run starts.

04 · How it gets built

Plan first.
Then earn the numbers.

01 — Validate the 7B configuration

Calculate the parameter count and memory requirements before committing to a long run.

02 — Add opt-in FSDP

Keep the existing 2B path working while adding sharded training, mixed precision and tested checkpoint handling.

03 — Prove training works

Run real training and verify that loss decreases instead of treating a successful launch as proof.

04 — Benchmark the checkpoint

Run the WikiText-103 evaluation and publish the measured perplexity. The ~9 figure remains a target until that happens.

05 · Reality check

No pretending.

Hardware

FSDP should make the 7B tier practical — if the node fits.

The actual GPU count, VRAM and communication overhead will be calculated against the rented multi-GPU node before training.

Results

~9 perplexity is not a promise.

The target is only a target. The public result will be whatever the trained checkpoint actually measures.

06 · Status

Verse 3 is being built.

The page is a living plan for the next model. As the work moves from architecture → training → benchmark, the plan will become a record of what actually happened.

Follow the build on GitHub ↗