Crate pointlock_store 

pointlock-store

RunLog + Checkpoint persistence (SQLite WAL via rusqlite, synchronous=FULL) and the content-addressed evidence area.

Authoritative design documents:

• docs/design/07-subflow-checkpoint-resume-repair.md §3 (checkpoint model, DDL, the four materialization moments, the actionIntent WAL transaction discipline, file-before-row-before-log, the rebuild-checkpoint self-check)
• docs/design/00-architecture-spine.md §6.1 (RunLog) / §6.6 (CheckpointView)

Shape of the API

• Store — the single-writer handle: Store::open, Store::begin_run, Store::append_event (seq allocation, insert, and checkpoint materialization in one transaction), Store::write_action_intent (the WAL entry whose committed return gates provider dispatch), Store::submit_human_response (the single-writer arbitration of human responses — first response wins, deadline judged by the store-receipt clock, shape-validated per purpose/mode; 06 §4.3), Store::put_evidence / Store::link_evidence, and the read side (Store::events, Store::run_meta, Store::run_status, Store::materialized_checkpoint).
• fold_checkpoint — the deterministic pure fold (RunMeta, events) → CheckpointView + RunStatus, exposed separately so it is directly testable; Store::rebuild_checkpoint and Store::verify_checkpoint (materialized == rebuilt, I1’s runtime self-check) are thin wrappers over it.

Append-only is structural: no API updates or deletes run_log rows (07 §3.3 rule 4 — re-judgement appends a new verdictRecorded carrying supersedes; old events never move).

The projection read side (R14, spine §10.2) homes in projection: the five renderer-agnostic DTO families + their query layer — the only contract any renderer (or pointlock locate) consumes.

Re-exports

pub use error::FoldError;

pub use error::HumanResponseRejection;

pub use error::StoreError;

pub use fold::FoldedRun;

pub use fold::RunMeta;

pub use fold::RunStatus;

pub use fold::fold_checkpoint;

pub use store::EvidenceMeta;

pub use store::EvidencePut;

pub use store::IntentDispatch;

pub use store::NewRun;

pub use store::RunListEntry;

pub use store::Store;

Modules

error

Error types of the store: fold-level (pure, structural), store-level (SQLite / IO / serialization plus the fold errors they wrap), and the typed rejections of the human-response arbitration (06 §4.3).

fold

Deterministic RunLog → CheckpointView folding.

projection

The projection protocol (spine §10, R14): renderer-agnostic read-only DTOs — the ONLY contract between any renderer and the store.

store

The single-writer SQLite store: RunLog append path, same-transaction checkpoint materialization, and the content-addressed evidence area.