Vault Operator is the only agent plugin I have found that puts block ids on the claims at ingest, so this is a gap question, not a wishlist.
The block id tells me which paragraph a claim came from. It does not tell me the words still match it. That breaks two ways. I edit a source note later and the claim in my sense making note quietly stops matching, while the link still resolves fine. Or the agent tightens a passage into something quote shaped at ingest, and nothing re-reads the block to check.
I built a small plugin for that one job, Cite Engine, live in the community directory. No AI in the check itself. It snapshots the quoted text, re-reads the source block, and flags anything that drifted or no longer resolves.
Is a fidelity check like that worth having inside Vault Operator, or would you rather point people at it?
Vault Operator is the only agent plugin I have found that puts block ids on the claims at ingest, so this is a gap question, not a wishlist.
The block id tells me which paragraph a claim came from. It does not tell me the words still match it. That breaks two ways. I edit a source note later and the claim in my sense making note quietly stops matching, while the link still resolves fine. Or the agent tightens a passage into something quote shaped at ingest, and nothing re-reads the block to check.
I built a small plugin for that one job, Cite Engine, live in the community directory. No AI in the check itself. It snapshots the quoted text, re-reads the source block, and flags anything that drifted or no longer resolves.
Is a fidelity check like that worth having inside Vault Operator, or would you rather point people at it?