Context should be abundant.
What if context is expensive because we keep reconstructing it?
An open notebook proposition: repeatedly reconstructing earlier state may be one reason context feels scarce. Indexing reusable state is a question to investigate, not an established saving.
Context is treated as expensive because we repeatedly reconstruct it.
Every new call re-derives what a previous call already established, at real token cost, because nothing kept the earlier state in a form worth returning to. If that state were indexed rather than discarded, context stops being the scarce resource everyone budgets around.
When does returning to state cost less than reconstructing it?
The notebook proposition needs measurements against a defined workload, including the cost of indexing and retrieval.
SOURCES & PROVENANCE
- Chris Hay’s existing notebook source
context-should-be-abundant.ts, recorded 26 August 2026. Imported as a draft; no historical publication date inferred.
AUTHOR / CHRIS HAY · VERSION / 0.1
REFERENCE THIS DRAFT
An unpublished working record. These references identify the draft and omit a publication date. They become version-specific publication citations when the record is released.
Chris Hay. Context should be abundant. [Unpublished draft, version 0.1]. https://chrishayuk.com/notebook/context-should-be-abundant