0ARCH Core
One person. One borrowed TPU. 47 starts.
This is the real record of Kisoku 1.6B, the language model 0ARCH trained from nothing. The line behind these words is its training loss, with every crash marked. Everything on this page comes from the log.
The whole story
1
person
524B
tokens of text seen
243,000
training steps
47
starts, after 46 crashes and restarts
$320
out of pocket, besides the free TPU grant
The log
What happened, in order, from the training log and the report. Nothing is smoothed over.
Aug 11
The grant ends
Google's TPU Research Cloud grant formally expires and a renewal is declined for capacity. The TPU keeps running because nobody reclaims it. From here on, every day of training is borrowed time.
Mid August
Stage 1 begins
A 1.6B-parameter model, 243,000 steps planned, about 2.1 million tokens a step, 13.3 seconds a step on a TPU v4-32 with four hosts. The first log file was not kept; the record starts at step 28,650 on August 23.
Aug 25
The first scar
Five restarts in sixteen hours from the step 38,000 checkpoint. Checkpoints are written every 1,000 steps, so each crash throws away up to four hours of work.
Sep 2
Thirteen deaths at one step
A failed read leaves a page of zeros in the data mount's cache. One worker reads it and quits, the other three hang at the barrier, systemd restarts everything from the last checkpoint, and it dies at the same page again. Thirteen times. The log tail looks healthy the whole time; the only real signal is that the newest checkpoint folder stopped advancing. Thirty hours pass before the cause is found by comparing bytes at the failing offset against the cloud copy.
Sep 4
The restart guard
The same bug, the same day, three more deaths and nine hours. After this a guard is written: a state file counts starts without a new checkpoint, and on the third one the script remounts the data and restarts itself.
Sep 9
The billing lapse
The billing account goes delinquent and cloud storage starts returning 403. The run dies at step 122,733 looking exactly like the mount bug, so the first fix is the wrong fix. Paid, the account reopens 24 minutes after the run died, and the next automatic restart picks up from step 122,000.
Sep 10 to 21
Three more rounds
The zero-page bug comes back on September 10 and 21, and single crashes land on the 15th and 18th. The guard catches the last one on its third start, as designed. Four incidents and roughly 50 hours lost over the run. Every one of them is on the curve below.
2.11.81.530K steps100K243KThe scars
Every tick on the line is a place the run died and restarted from the last checkpoint: 47 starts in all. Tap one.
Stage 1: learning language
199,000 steps of general text. The loss falls fast, then slowly, as the model works out how language fits together. The September preview was cut at the end of this stage.
Stage 2: math and code
25,000 steps with much more math and code in the mix, aimed at the preview's weakest spots. Part of the sudden drop is the new data being easier to predict.
Stage 3: cool-down
The last 19,000 steps. The learning rate winds down and reasoning examples come in, so what it learned settles. The release is built on the end of this line.
Training loss, lower is better. Each point averages 1,000 training steps, about 1.5 billion words, from our run log. The log starts at step 28,650; earlier steps weren't kept.
Sep 22
Stage 1 ends, and the plan is found broken
Step 198,999 at 14:53 UTC. The notes say PRETRAIN FINISHED. That afternoon it turns out the launcher for stages 2 and 3 was lost in a laptop migration and only stage 1 ever ran, so the learning rate never came down. The stage 1 checkpoint is eleven hours from automatic deletion; it gets copied out by hand, and stage 2 starts at 22:29 the same night with far more math and code.
Sep 27
Stage 3 and the truncation default
Stage 2 ends on the 26th. Before stage 3, a framework default is found cutting every document at 4,096 tokens, which had been throwing away the answers on the long reasoning data. Fixing it breaks the saved data-iterator state; the state gets patched by hand after a test on a toy pipeline. Stage 3 runs the cool-down and finishes on September 30 at 02:48 UTC with a clean exit.
Oct 1
The bug that hid the scores
While chasing why the model answered a counting question with nothing at all, the export script is found shipping a repetition penalty in the generation config. The evaluation harness kept it; none of the baselines had one. Every generation score had been understated for weeks. Removed, counting accuracy goes from 4.0 to 41.3. The same day the 32K context phase ends and the 64K phase begins.
Oct 4
The last checkpoint
Phase C, 64K context with synthetic long-document tasks, writes its final checkpoint at 15:24 UTC. 524 billion tokens seen. Chat fine-tuning starts the same day: nine passes by October 6.
Watch it learn to talk
The same prompt, given to four real checkpoints from oldest to newest. Greedy decoding, first 48 tokens, copied word for word from the log.
Prompt
Once upon a time, in a small town by the sea,
Kisoku v1
1/4Early 2026. 3B parameters, about 60B tokens.
a small town by the sea, a small town by the sea, a small town by the sea, a small town by the sea, a small town by the sea, a small town by the sea, a small town by the sea
Stage 1
2/4September. 1.6B parameters, 414B tokens. The preview was cut here.
there lived a young boy named Kai. Kai was known for his mischievous grin and his love for adventure. One sunny afternoon, while playing in the park, Kai discovered a hidden treasure chest. The chest was filled with shiny coins and
Released base
3/4October 10. 524B tokens, after stages 2 and 3 and long context.
there lived a young boy named Max. Max was a curious and adventurous child who loved exploring the world around him. One day, while playing in the park, he discovered a mysterious box hidden under a tree. Inside the box was a small
Chat preview
4/4The base model after nine fine-tuning passes.
Once upon a time, in a small town by the sea, there lived a young boy named Jack. Jack was a curious and adventurous boy who loved to explore the world around him. One day, while playing in the nearby beach, he
Base models continue text, they do not answer, so repeating the question or running on is normal for them. v1 was run in full precision because it overflows in bfloat16. Nothing here is generated live.
Oct 7
Ten benchmarks, one harness
Every model in the tables runs through the same evaluation harness on the same machine. The home 4090 goes offline overnight and the last runs finish on a second box. Five wins each against Meta's Llama 3.2 1B, which trained on about 18 times more data.
Ten benchmarks, one harness
Kisoku against Meta's Llama 3.2 1B, which trained on about 18 times more data. Five wins each: Kisoku on reasoning and math, Llama on knowledge and commonsense.
Kisoku 1.6BLlama 3.2 1BPercent correct, higher is better.GSM8K
Grade-school math word problems
Kisoku 1.6B: 15.0Llama 3.2 1B: 5.8MMLU
Multiple-choice questions across 57 school and professional subjects
Kisoku 1.6B: 34.2Llama 3.2 1B: 31.3ARC-Easy
Grade-school science questions
Kisoku 1.6B: 64.4Llama 3.2 1B: 61.8ARC-Challenge
The harder grade-school science questions
Kisoku 1.6B: 40.1Llama 3.2 1B: 36.9BBH
Hard multi-step reasoning puzzles
Kisoku 1.6B: 28.6Llama 3.2 1B: 28.3PIQA
Everyday physical commonsense
Kisoku 1.6B: 73.0Llama 3.2 1B: 74.9WinoGrande
Working out what a pronoun refers to
Kisoku 1.6B: 56.8Llama 3.2 1B: 60.5HellaSwag
Picking the sensible ending to a short scene
Kisoku 1.6B: 57.8Llama 3.2 1B: 64.2HumanEval
Writing Python functions that pass tests
Kisoku 1.6B: 14.6Llama 3.2 1B: 18.9TriviaQA
Trivia recall
Kisoku 1.6B: 23.1Llama 3.2 1B: 40.7
Both models ran through the same harness on the same machine. Qwen2.5 1.5B and SmolLM2 1.7B are ahead of both on most of these tests. Full table and long-context results
Oct 7
Out to 128K
The long-context runs, 4K to 128K, against the same baseline. Ahead at four lengths, behind at one, level at the last.
It can read a whole book at once
Kisoku was trained to 64K tokens of context, about 200 pages, and reaches about 128K with YaRN at inference. RULER scores retrieval and reasoning over long inputs.
Kisoku 1.6BLlama 3.2 1BRULER, 13-task mean, higher is better.806040Kisoku 1.6B 76.1Kisoku 1.6B 66.2Kisoku 1.6B 64.2Kisoku 1.6B 58.8Kisoku 1.6B 56.7Kisoku 1.6B 43.2Llama 3.2 1B 73.5Llama 3.2 1B 67.4Llama 3.2 1B 61.9Llama 3.2 1B 56.7Llama 3.2 1B 49.2Llama 3.2 1B 43.14K8K16K32K64K128KContext length, thousands of tokens
Same harness and settings for both. Kisoku is ahead at 4K, 16K, 32K and 64K, behind at 8K and level at 128K. Granite 4.0 1B and Qwen3.5 are ahead of both at every length, and part of Kisoku's score is format familiarity from its training mix. Full long-context table
Oct 10
Release
Weights, intermediate checkpoints, the chat preview, GGUF builds, training and evaluation code, raw evaluation outputs and the full report, all Apache 2.0. Out of pocket for the whole run: about $320. The TPU was a grant. The rest was one person and time.
Ask it something
Real answers from the released chat model, copied word for word from our test log. Tap a question to replay one.
You
Who are you?
KisokuI'm Kisoku, a small open language model built from scratch by 0ARCH. I run on a laptop and handle everyday stuff like answering questions, writing, and code.Replay of a real answer from our test log, 37 tokens
Kisoku
A small, free language model that runs offline on your own laptop, so nothing you type leaves your computer. Released in October 2026, it matches Meta's Llama 3.2 1B on ten benchmarks after training on about 18 times less data. The chat version is still a preview and can lose the thread in long conversations.
- Size
- 1.6 billion parameters
- Runs
- Offline on a laptop, through Ollama
- License
- Apache 2.0
- Status
- Released October 10, 2026 (chat: preview)
$ ollama create kisoku -f Modelfile$ ollama run kisoku
After downloading the model file. Full steps
AI built for your business
The same work, pointed at your problem. Fixed price, and you own the code.
A private AI on your own hardware
An open model running on a machine in your office, with a chat window your team can use. Nothing anyone types goes to an outside AI company.
Answers from your own documents
Ask questions about your manuals, contracts or past jobs and get answers that point to the page they came from.
Paperwork that fills itself in
AI that reads the emails, invoices and order forms coming in and puts the details into the system you already use.