Context as trajectory through semantic space

A statistical language model asks: given what has been said, what is most likely to be said next? A geometric context model asks a different question entirely: given what has been said, where are we right now in the space of meaning?

These are different questions requiring different computational structures. The first output is a token. The second output is a location. Knowing where you are is the primary output of a geometric context model. Generating text is optional and secondary.

Each word moves the current position. Strong semantic content carries weight. Function words and discourse markers nudge the trajectory. The path has direction, velocity, and history. That path is context, represented not as a list of tokens to cache, but as a single geometric state that captures where the conversation has been.

The state is inspectable at any moment. You can ask it where the conversation sits on the temperature axis, or the dominance axis, or the valence axis. These are questions with precise geometric answers, not probability distributions over vocabulary.

What makes it geometric context modeling

Geometric

Meaning is position

The space has defined axes, distances, and directions. Every word has a coordinate. The geometry is the representation, not a description of it.

Context

Context is a trajectory

The system models where a conversation is, not what word comes next. Context is the geometric path through the space, maintained in 52 bytes regardless of conversation length.

Modeling

The model is the trajectory

A continuous, dynamic representation that can be queried and reasoned over at any point. The state is the model. The model is the path.

Both are chains of thought.
The chain is in different places.

This is the question anyone familiar with transformer reasoning will ask: how does GCM reason? The answer is that it does, continuously, whether or not anything is written down. The chain of thought is the geometric trajectory itself.

Transformer chain of thought

The reasoning is the text

A transformer reasons by externalizing intermediate steps as tokens. The reasoning only exists insofar as it has been written out. When context shifts, earlier tokens remain in the sequence and the attention mechanism must reconcile them. Longer chains require more compute because each token attends to everything before it.

Computational primitive: token sequence

GCM chain of thought

The reasoning is the movement

GCM reasons through movement. Each word shifts the SSM state along 13 semantic axes. The reasoning is encoded in the geometric path. The thought happened geometrically even when nothing was generated. Context shifts are absorbed by per-axis decay rates. The chain is always present and inspectable after any word with no prompting required.

Computational primitive: geometric trajectory

The key distinction: A transformer writes its reasoning down in order to reason. GCM reasons whether or not it writes anything down. The reasoning does not degrade if a step is skipped, because no steps are ever skipped. The trajectory is complete by definition.

Scope and honest limits

Not a replacement for generation

GCM handles context. A generation layer handles words.

Geometric Context Modeling does not replace language generation and does not compete with it. A generation layer of any kind can sit above a GCM without changing how the context model operates.

Not a rejection of statistics

Statistics produced the map. Geometry navigates it.

The GloVe embedding that defines the geometric space was trained using statistical learning. Statistics and geometry are complementary, not competitive.

Not a claim about everything

Physical universals work. Cultural constructs have a ceiling.

Physically grounded dimensions encode cleanly. Culturally contingent dimensions require supplementary grounding. The architecture is honest about this in a way statistical models cannot be.

Not image or voice generation

GCM operates in semantic space, not signal space.

Images and voice are continuous signals requiring different architectures. GCM's generation capabilities apply specifically to text and code, where output is discrete, structured, and semantically constrained.