that's what we started with, exactly because of the human review part. however we soon found out that there will be a lot of merge conflicts in the text (usually markdown) which heavily depends on the instructions and structure of the data. that's why for Markbase we opted for etag based validations to avoid any potential of conflicts.
Comments
What if the memory were git repo backed, and the FTS5 were a speed-specific optimization?
Then the memories could easily be human-reviewed. The repo would be the canonical source, and the FTS5 would be one specific materialization.
that's what we started with, exactly because of the human review part. however we soon found out that there will be a lot of merge conflicts in the text (usually markdown) which heavily depends on the instructions and structure of the data. that's why for Markbase we opted for etag based validations to avoid any potential of conflicts.