concengine
01 — observation

The lattice prefers stillness.

a quiet engine —
events arrive in their order /
nothing is hurried

02 — engine

concengine is a concurrent event simulation engine. It receives logical events on a discrete tick lattice, synchronizes parallel timelines at named barriers, and replays the same history to the last byte — not because it remembers, but because it never had to forget.

Three primitives. One promise: deterministic calm in a chaotic event space.

03 — barrier

Where timelines rejoin.

03a — fork

two paths from one tick

03b — join

two paths into one accepted history

04 — replay

The same thirty ticks, twice.

Forward and replay overlay perfectly. Determinism is shown as registration — not as a promise, but as a picture in which two pictures cannot be told apart.

the river writes once /
the river is reread /
the river is the river

05 — listening

10M

events per second, observed without strain

one tick, then another /
the lattice listens /
nothing drops

06 — invitation

There is no signup. There is no demo to schedule. There is one quiet way to begin.

a single tick will run, locally, in a paper-quiet terminal.