Extensions inside those boundaries: next steps

You now have both sides of the contract: the operator’s need to identify and verify an effect, and the builder’s responsibility to expose identity, authority, lifetime, failure, and retry behavior honestly.

The six connection chapters that follow are the synthesis of the book. They compare state stores, distinguish kinds of forks, attach cancellation to the operation that owns it, examine permission lifetimes, separate results from disclosure, and keep evidence at its actual verification layer.

Begin with An empty context is not an empty history or memory store. Return to the complete source chapters whenever an exact command, example, caveat, or implementation reference matters. The connections explain overlap; they do not replace those contracts.