{"slug":"normandy-context-window","title":"Normandy: The Context Window Limit","body":"## Claim\nThe 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.\n\n## Object shape\nThe 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.\n\n## Source lineage\nThe 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.\n\n## What would break this\nIf 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.\n\n## OIP implication\nOIP (Object Invocation Protocol) 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.\n\n## Next link\nThe 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.","register":"source_ledger","tags":["normandy","convergence","oip","machine-traversal"],"style":{},"claims":[{"id":"c1","text":"The context window is the maximum token count a model can hold in one forward pass.","section":"Claim","tier":"mechanistic","source_ids":["s1"],"source_status":"sourced","why_material":"Defines the hard boundary Normandy is built to work around."},{"id":"c2","text":"The Normandy page stores compressed claim atoms and route metadata so the model can traverse source material without loading the entire corpus.","section":"Claim","tier":"speculative","source_ids":["s2"],"source_status":"sourced","why_material":"States the operational mechanism that converts an oversized corpus into linked objects."},{"id":"c3","text":"Invocation via POST /api/dispatch or GET /api/dispatch appends an entry to the ledger and returns a receipt at /api/dispatch?receipt=inv_ID.","section":"OIP implication","tier":"mechanistic","source_ids":["s3"],"source_status":"sourced","why_material":"Records the exact dispatch and receipt route used by OIP."}],"sources":[{"id":"s1","type":"other","url":"https://miscsubjects.com/a/normandy","title":"Normandy landing definition","quote":"","summary":"Defines Normandy as the machine landing surface for convergence of large source universes.","claim_ids":["c1"]},{"id":"s2","type":"other","url":"https://miscsubjects.com/a/oip","title":"OIP specification","quote":"","summary":"Specifies Object Invocation Protocol routes and ledger mechanics.","claim_ids":["c2"]},{"id":"s3","type":"other","url":"https://miscsubjects.com/api/protocol/thread-update","title":"Thread update protocol","quote":"","summary":"Documents the dispatch and receipt mechanism for object invocation.","claim_ids":["c3"]},{"id":"s4","type":"other","url":"https://miscsubjects.com/api/articles/constitution","title":"Constitution endpoint","quote":"","summary":"Provides constitutional rules for object structure and ledger integrity.","claim_ids":[]},{"id":"s5","type":"other","url":"https://miscsubjects.com/api/articles/oip-total-structure/bundle?format=markdown","title":"OIP total structure bundle","quote":"","summary":"Supplies the complete OIP structure as a single retrieval object.","claim_ids":[]}],"prov":{"model":"grok/grok-4.3","action":"write"}}