Six years in: where this engine comes from

The public record of this programme is compressed: a development log that begins in July 2026, specifications arriving weeks apart, an engine live to try within the month. Read alone, it suggests a system invented at speed. It was not. The engine has been in design since 2020, under a private working name, and the public weeks are the implementation of decisions that took years to make.

The positions that define the architecture were not adopted quickly. Determinism over statistical inference, repair before response, a language-blind engine separated from a content-addressed language artefact, records rather than explanations: these are the residue of six years of watching the alternatives and deciding, repeatedly, not to ship them.

A company that asks buyers to value derivability should be able to derive itself. The origin is stated here so the compressed public timeline cannot be mistaken for the whole history, in either direction: the design is older than the log, and the working engine is exactly as young as the log says it is.

The basis for this page is stated rather than measured. It is the founder's dated record, and it carries the same rule as every other figure on this site: if it is ever contradicted by evidence, it will be struck here, not deleted.