timeline/timeline.yaml.
This guide explains that record at the linked revision, which includes the 0.121.0 and 0.123.0 engine releases. Read
releases for the automatically synchronized publication index,
historical milestones for the original dated accounts,
current status for the released engine, and
the roadmap for forward plans.
Eras
These are historical periods, not support branches or instructions to use an old
grammar. Use the current reference when authoring a workflow.
Evidence classes
The source’s
timeline/verify.py
checks mechanically verifiable references. Testimony and private archives keep
their labels; they do not become public proof. This page describes the checking
contract and does not claim that a fresh verification run has just passed.
Gates
Forward entries describe conditions to satisfy, not promised release dates. A gate being listed is not evidence that it has closed. Follow its source and the dated evidence before interpreting it as a delivered capability. One example referenced by the roadmap is the hundred-year gate (conformance, archival, compatibility, deterministic checking and succession). It is a condition in the cited revision, not a release announcement. The cited revision also lists a Connectome gate that required the whole memory subsystem before a 1.0 release. The engine roadmap retired that umbrella on 2026-10-08. 0.124 is the current release line. Work stays focused on maintenance, security and the media capabilities workflows need; native video is planned for 0.125. No 1.0 release is planned. Read that entry, and the other forward gates of that plan, as history rather than as pending work. The record is append-only: a correction adds a note rather than silently rewriting an earlier claim. The roadmap gives the wider context; crate admission explains the engineering admission process.Released implementation
Find the engine snapshot used by the current documentation.
Sources and synchronization
Understand revision pins and the limits of each kind of evidence.