paper
Paged Context Memory: Runtime Systems for Evidence Blocks, Locality, Speculation, Linking, and Policy Preservation
Paper 2 extends the trilogy from semantics into runtime behavior. It argues that compiled context should live like managed memory: evidence blocks enter working sets, locality governs movement, speculative execution prepares likely futures, context GC removes dead state, and provenance remains attached through lifecycle transitions.
Abstract
Compiled context needs a runtime, not just a representation. This paper treats context as a semantic runtime built from evidence blocks, working sets, locality-sensitive movement, speculative preparation, garbage collection, linking, provenance, and policy-preserving lifecycle transitions.
Why it matters
Even a strong IR is not enough if compiled context decays once it enters execution. Enterprise systems need locality, lifecycle management, provenance, and policy preservation at runtime so context remains legible, efficient, and governable after compilation.