Ask for access
Ask for access
How it works
Every line an agent runs becomes a typed event: its shape, its steps, what each step touches, and a hash that keeps it as written. Your rules are checked against the steps, not the text.
Before it reads the steps, Olki names the shape of the line. Across 33,000 lines from 40 sessions, fewer than one in ten was a single command.
Read by olki shapes on one machine, October 2026. Lines from test folders are left out.
Every step, in every shape, is described with the same four words. A rule is written in them too, so the two can be compared exactly.
Each step declares what it touches. Olki follows what each step hands the next, adds up what the line needs, and finds the rule that allows each part.
The same line, under a build server's rules, in both modes, one moment at a time.
A session is the turns you started. A turn is everything that followed one prompt, the helpers an agent started included. Each step is a typed event under its own id. This is one real session, zoomed three times.
A change counts as verified only when a check ran after it and passed. A claim is held up against the events it cites.
Deleting a session's own trail, or changing Olki's rules, is marked in shadow and stopped in enforce. The agent cannot edit what it is checked against.
Measured on one machine in October 2026: 9,372 decisions, and 6,316 lines from its busiest session.
Olki is in private release. Installs use a token we send you.