Architecture / ownership

Meaning above machinery¶

Tokimu is a state-processing runtime. It accepts input, rules, assets, and time, then produces updated world state and observable output.

Its central ownership chain is:

Corpus and applications
          ↓
   World graph / state
          ↓
 Systems, signals, rules
          ↓
      State change
       ↙       ↘
Presentation  Synchronization
       ↓             ↓
Renderer / Platform / WASM / Transport

The trusted center¶

The world model owns simulation truth. Rendering, platform integration, authoring tools, persistence, and networking adapt or observe that truth. Useful capabilities do not automatically belong in the kernel.

Foundational services¶

Services such as rendering, input, assets, diagnostics, and presentation expose Tokimu-owned contracts while concrete providers remain replaceable. Font files, GPU backends, icon libraries, sockets, and browser APIs should not define the engine's semantic model.

Application ecosystems¶

Tokimu aims to make specialized applications straightforward to build without absorbing them into the engine. A game, CAD workbench, robotics dashboard, or technical simulator may own very different domain meaning while sharing the same runtime services.

Tokimu is a Rust engine with an intended TypeScript-first authoring surface. TypeScript gives authors syntax, types, and tooling; it lowers into or communicates through Tokimu-owned semantic contracts rather than becoming an alternate runtime kernel.

Architectural maxim

Own meaning. Delegate implementation.

Source documents¶

The repository currently treats these documents as architectural truth: