This release is a bounded reference, not an exactly-once distributed executor. Its only effect is replacing a list in the same SQLite transaction that retains the request, revision and receipt. SQLite/OS/storage guarantees, privileged file integrity and host isolation are assumptions. Process rollback and independent connections are tested; hardware power failure is not.

A coherent old database has the same epoch and valid hashes. The restore-limit test deliberately demonstrates that it can be replayed. **After recovery or uncertain continuity, stop dispatch and reconcile against a trusted external latest-history anchor; never automatically resend merely because the local database says absent.** No external continuity service ships here. Likewise, a new key is a new intent, so automatic key replacement after a lost response can duplicate a business effect.

All export contents are privileged evidence. Native records and manifests do not enforce read rights. Serve them only through host-controlled projections. `validate_snapshot` and `verify_export` establish internal consistency and file closure relative to the supplied cut, not authenticity, authority, completeness against the world, or the latest cut. Native outer schemas alone do not validate nested action meaning.

The package does not implement delegation chains, impersonation, use counters, remote effects, durable distributed sagas, receipts from third parties, arbitrary descriptive-action invocation, operational credentials, legal mandate validation, force cancellation of an already committed effect, erasure, per-field disclosure, or production history restoration. Retired keys retain the complete immutable intent and receipt in this fixture; this is not a compliant deletion mechanism.


R2 adds atomic 10,000-row capacity bounds, a reserved final global policy revocation, complete operation replay, and portable record filenames. At capacity, never replace a retry key or silently start a new store. Same-pin compensation is unavailable after definition retirement. An interrupted export with a torn file needs a fresh directory; between-files interruption can resume the exact cut. Test installations retain the mandatory snapshot and manifest inside the Dimension and label the model lock candidate/simulationOnly.

The global event limit can be exhausted by a caller holding even one current right; host rate/admission limits are mandatory and are not implemented here. Lifetime capacity is at most about 3,333 pending submissions or 2,500 first commits before other Events. Caller event projections omit global counters; privileged archives retain them. Each new test installation includes all adoption documentation and requirements (nine pinned files).