Structs§
- Device
Join Bootstrap Activation - Device
Join Bootstrap Commit - Device
Join Bootstrap Plan - Device
Join Bootstrap RowData - Everything one bootstrap commit needs to materialize its rows, for a commit the joining database does not already cover through an installed snapshot.
- Installed
Replay Baseline - The replay baseline a device stands on, as the history verifier needs it.
- Membership
Authority Bytes - Merge
Retraction Cleanup Input - Owned
Verified Merge Materialization - Prepared
Merge Materialization - Prepared
Merge Materialization Package - Resolved
Device Join Bootstrap - A bootstrap plan together with the row data for every commit in it the joining database does not already materialize. Installation only accepts this shape, so a bootstrap can never advance its position over commits whose rows were never resolved.
- Retained
Commit Activation Input - Retained
Merge Materialization Input - Retained
Merge Materialization Key - Verified
Acknowledged Store Snapshot - One snapshot verified as acknowledged by every device active at its cut. Reclaim deletes history behind a snapshot only against this, and carries the acknowledgements it names as the claim’s evidence.
- Verified
Merge Materialization - Verified
Merge Membership Objects - Verified
Replay Baseline Retirement Proof - A snapshot verified against every writer active in current Store authority.
Local replay retirement requires this stronger proof; cloud reclaim keeps
using
VerifiedAcknowledgedStoreSnapshot. - Verified
Store Snapshot Authority - One snapshot verified as installable: its signed metadata, the cut it covers, and the devices and registrations active there. A device installs its baseline from this and verifies everything that arrives afterwards against it.