Work bounds under the entry contract #
A requested entry domain, fitting input words, well-formed memory and the client's valid history may justify both its safety conditions and its local-work bound. These consequence rules keep the original emitter, scratch bank and exchange factor. They change neither the program nor its whole-memory and register-frame guarantees, and introduce no new execution model.
Main results #
Realizes.consequence_work: compare work under the requested entry contract.RealizesBounded.consequence_work: the same rule retaining frontier-bounded accesses.
The rules are original infrastructure over the existing realization contracts.
Strengthen safety and compare local work under the requested entry domain and the client's valid history. The emitter, scratch size, exchange factor and width freedom are unchanged.
Strengthen safety and compare local work under the requested entry domain and valid history, retaining frontier-bounded accesses and all of the original witness resources.