Module history_mode
Expand description
Window-independent projection of a managed record’s historical states.
The controller reads a rolled-back clone of the live Automerge document. It therefore neither commits an app’s open transaction nor gives a historical renderer access to a live record, persistence, or dispatch.
Modules§
- adapter
- Pure adapter utilities. Domain allowlists, schemas and presentation remain local.
- capability
- How a widget takes part in document History: the capabilities an app root or a document owner provides, and the walks the runner uses to reach them.
- checked_
files - Typed checked-file state. No Automerge identity or document fallback exists here.
- pending_
controls - Finite custody for live controls that were queued before History opened.
- preview
- Presentation-only inputs. No live widget, document loan or service enters a preview.
- registration
- Explicit ownership and presentation registration for managed roots.
- restore
- Checked content-only historical restoration. The caller owns authorization and commit.
Structs§
- Framework
History Surface - Frozen
Preview Assets - Keys are immutable historical content hashes admitted by the source owner. Absence is an unavailable historical asset, never a request for current bytes.
- Historical
Asset Request - A source reads only this immutable selected version when resolving media.
- Historical
Asset Response - A single request-bound completion capability, never a live document handle. The provider cannot relabel an old result with another request’s identity.
- History
Controller - History
Definition - History
Owner - Captured by the actual mounted owner; callers cannot manufacture custody.
- History
Registration - History
Resource - Full authority namespace for one historical resource.
- History
Scope Definition - History
Snapshot - Immutable Automerge bytes at one exact causal frontier.
- Managed
Root - Preview
Accessibility - Descriptions and closed page-navigation targets only; never arbitrary actions.
- Preview
Input - Preview
View - Restore
Review - Opaque proof that a particular selected state was reviewed against a particular live frontier. Validation grants no authority and writes nothing; the host must separately recheck permissions before restoring.
Enums§
- History
Error - History
Presentation - History
Registration Error - History
Source Registration - Immutable identity supplied by the owning runner. This carries no document. Bound runners resolve their actual checkout instead of accepting a foreign identity.
- Preview
Navigation - Preview
Side - Which exact frontier of a selected change or group is being previewed.
Constants§
- HISTORY_
PAGE - How many of the newest changes a history view describes when it opens, and how many more each request for earlier ones adds. Describing a change costs a replay step, so a long history opens at its latest page instead of replaying everything.
Traits§
- Historical
Asset Source - Host-registered resolver. It may complete immediately or on a worker; the same captured response key is checked on the owner thread in both cases. The trusted domain resolver derives content-hash references from the supplied immutable snapshot, not a live record or current media path. The framework checks response custody and byte integrity; it cannot infer a domain’s media schema. A missing recorded hash must remain unavailable.
- History
Preview