---
slug: normandy-context-window
title: Normandy: The Context Window Limit
canonical: https://miscsubjects.com/a/normandy-context-window
---

## Claim
The context window is the maximum token count a model can hold in one forward pass. Normandy treats this limit as a hard mechanical boundary rather than a temporary engineering inconvenience. The page object stores compressed claim atoms and route metadata so the model can traverse source material without loading the entire corpus at once.

## Object shape
The Normandy page carries a readable body, a claims array, source lineage records, provenance fields, review entries, a bundle route, and traversal metadata. The body section holds the operational explanation. The claims array stores atomic assertions with tier labels and source references. The source lineage records point to ledger entries and external URLs. Traversal metadata lists next-link and bundle routes so the model can continue without re-loading prior context.

## Source lineage
The page references four ledger objects: the Normandy landing definition at /a/normandy, the OIP specification at /a/oip, the constitution endpoint at /api/articles/constitution, and the thread-update protocol at /api/protocol/thread-update. Each source entry records the URL, the object type, and the claim identifiers it supports. The bundle route at /api/articles/oip-total-structure/bundle?format=markdown supplies the full OIP structure as a single retrieval object.

## What would break this
If the page omitted the source lineage array, the model would have no verified route back to the original material and would be forced to guess or hallucinate content. If the claims array lacked tier labels, the model could not distinguish human data from mechanistic inference or speculative projection. If the next-link field were absent, the model would reach the end of its context with no defined continuation path.

## OIP implication
OIP ([Object Invocation Protocol](/a/oip)) treats the Normandy page as a work object. Invocation occurs via POST /api/dispatch or GET /api/dispatch with the page slug as the key. The dispatch appends an entry to the ledger and returns a receipt at /api/dispatch?receipt=inv_ID. The receipt contains the object hash, the timestamp, and the list of claim identifiers served. Subsequent invocations can reference the receipt to replay or repair the same object without re-transmitting the full body.

## Next link
The next link is the OIP total structure bundle at https://miscsubjects.com/api/articles/oip-total-structure/bundle?format=markdown. That object supplies the complete protocol definition and the full set of route schemas required for continued traversal.
