Persistence, transactions and consistency
Reference: This page is a source-based technical synthesis of the LaTeX chapter cited below. For exact syntax, availability or ABI signatures, verify the versioned source, manifest and executable tests.
Scope and source boundary
Atomic transaction scope, persistence and eventual synchronization are distinct guarantees.
Collections, datasets and cursor-shaped views are ways of accessing and projecting application data. The source differentiates query semantics, persistence providers, transaction scope and runtime object lifetime. A cached result must not be confused with a domain decision or an authoritative write.
Engineering rules
- Select the collection or dataset shape required by the query.
- Track cursor and provider lifetime at the owning runtime boundary.
- Make transaction and consistency scope explicit for writes.
- Treat projections and view caches as invalidatable derived state.
Chapter outline (original LaTeX headings)
- Conceptual Identity
- Consistency Across Facets
- Transaction Boundaries
- Process-Level Consistency
- Design Rules
- Summary
LaTeX provenance
Primary chapter: Declarative Conceptual Programming with the logiCells Platform/developer-guide/chapters/transactions-consistency-and-identity.tex.