Module atomic_message 

Atomic multi-note write primitive: commits a set of notes — each with its FTS document and its kind-selected embedding model rows — in ONE writer transaction, instead of one create_note call per note.

Built for khive-pack-comm’s dual_write_message (outbound + inbound copy of a comm.send/comm.reply), which previously cost roughly a dozen separate writer acquisitions per send: two create_note_inner calls (row + FTS + one vector insert per registered model each) plus a root-send thread_id patch. Shaped as create_notes_atomic_with_report(Vec<AtomicNoteSpec>) rather than a comm-specific pair primitive so other multi-write verbs can share the same preparation. Keyed memory.remember appends a required annotation and final key claim before committing its prepared plan.

Embed-first

Embedding is slow compute (network/model calls). Every distinct content’s embeddings, across the selected models, are computed before any transaction opens — the writer is held only for synchronous DML, exactly like the rest of the ADR-099 atomic-unit machinery (atomic_plan/atomic_runner). This is the same reason atomic_prepare::prepare_add_note defers vector indexing to a post-commit PostCommitEffect::ReindexNote; the difference here is embeddings are computed before commit instead of after, so the vector rows land in the SAME atomic unit as the note row and FTS document, and no post-commit reindex is needed at all — every plan built by create_notes_atomic_with_report carries post_commit: PostCommitEffect::None.

One writer acquisition

Each note becomes its own AddNotePlan; every spec’s plan is applied by ONE crate::atomic_runner::run_atomic_unit commit pass — one khive_storage::SqlAccess::atomic_unit, one writer checkout, one WAL commit for the whole set. A failure on any note’s plan rolls back the ENTIRE unit (atomic_runner’s documented guarantee: a later op’s failure unwinds even an earlier op’s own already-RELEASEd SAVEPOINT), so a crash or guard failure partway through never leaves an orphan copy — the process-crash gap the two-call version of dual_write_message used to document is closed by construction.

Structs

AtomicNoteSpec

One note to write as part of an atomic set. Mirrors the subset of create_note_inner’s parameters comm.send/comm.reply actually use — no annotates, salience, decay_factor, embedding_content override, or explicit embedding_model pin. Keyed-memory preparation carries those through internal options without changing the public multi-note spec.

Functions

create_notes_atomic_with_attachments

Create notes and their role-keyed attachments in the same writer transaction. The existing note, FTS, vector and revision accounting is preserved.

create_notes_atomic_with_report

Build and commit notes with an embedding-truncation report. The report keeps logical per-note/model accounting even when identical content shares one provider result, and is returned only when the whole note set commits successfully.