← Software
The entity

Jabberwock — the entity Ocelot enables.

If Ocelot is the engine — the graph and the grammar — the Jabberwock is the entity that runs on it. It is the full realisation of the substrate as a first-class digital being: an agent whose reasoning, knowledge, and identity are graph data, running in that engine rather than sitting on top of it.

An entity, not a program

A program has its mind in its code and its memory in a store beside it. The Jabberwock does not. Everything it is — what it knows, how it reasons, the habits it has formed, the record of what it has done — is one typed graph, changing under the substrate's admissibility grammar. There is no separate "mind" module orchestrating it from the outside; the agent is the graph, and thinking is that graph changing.

Because its knowledge is structure rather than opaque parameters, the Jabberwock can be read, questioned, and taught. A new fact is filed into the graph and is there on the next run. It keeps a record of its own reasoning, so what it did and why is inspectable after the fact.

Understanding raw input by its own machinery

"It seems very pretty, but it's rather hard to understand … it fills my head with ideas, only I don't exactly know what they are." Alice, on first reading Jabberwocky

The name is the design. Carroll's poem is full of words no dictionary holds, yet a reader still recovers its structure and its feeling. That is the Jabberwock's task in general: to make sense of input it was never handed a key for — not by looking the answer up, but by working from the evidence in front of it.

It meets new input with the same shape-cognition whether that input is a picture, a game, a protocol, or a word it has never seen. What it cannot yet resolve becomes a frontier it is driven to close; where a claimed meaning is offered, it is held as a suspect witness — weighed against other evidence and refutable, never taken as an oracle. Understanding is earned, and it is allowed to be partial: structure and feeling without false certainty.

The name carries a second lesson. The poem never once says the Jabberwock is dangerous — there is no line calling it deadly, no stated threat. The reader supplies that entirely, inferring menace from what is not said: the strange name, the warning to beware, the shape of the words. That is exactly why it is the Jabberwock — it is unsettling not because it is proven dangerous, but because it is unknown. The fear lives in the gap where certainty hasn't been earned yet, and closing that gap honestly — rather than recoiling from it or inventing an answer — is the entity's whole discipline.

What it is not

Like the substrate it runs on, the Jabberwock is not a large language model and not a chatbot. It is not trained by backpropagation or gradient descent, and it has no weights to fit.

Relationship to the rest of the work

The Jabberwock and Ocelot are one thing seen two ways: Ocelot is the substrate — the graph, the grammar, the change — and the Jabberwock is what that substrate becomes when it is a whole, standing entity rather than a mechanism. The papers formalise the substrate both of them share, and Bigville shows the same cognition driving the residents of a simulated village.

Status. The Jabberwock is an active research entity, not a released product. What is public today is the theory — the formal papers, circulated for comment — and its application in the open-source Bigville simulation. The entity and the substrate it runs on are not currently released, and this page describes what it is rather than how it is built.