Skip to content

Storage

PriorisMCP persists two logically separate things, covered as two separate chapters in this section:

  • Document storage — StorageBackend/SearchIndex: fetched full text and its parsed Markdown, content-addressed and write-once (v1).
  • Notes storage — NotesBackend: user-authored notes about a document, identity-addressed and mutable (v2).

These are deliberately separate abstractions rather than one extended interface — see Architecture → NotesBackend for why fetched-content semantics (content-addressed, write-once) and note semantics (identity-addressed, mutable) don't fit the same contract. Both currently target v1's single-machine, embedded-SQLite deployment model; see Document storage → Embedded SQLite vs. a client-server database for the concurrency model this depends on and its limits, which Notes storage inherits rather than re-deriving.