Keep knowledge current

Give each source an owner

Decide who maintains each policy, procedure or collection. Record where the authoritative copy lives and who approves a change.

Keep drafts and superseded documents outside the approved scope where possible. More documents are not a substitute for well-maintained knowledge.

Verify updates end to end

Changing a file does not guarantee an immediate change in answers. For sync-capable connectors, inspect the latest sync status and errors.

1. Update and approve the original document.
2. Check scope and run or await the configured sync.
3. Ask a known question affected by the change.
4. Open the citation and verify the updated content.

Handle old content explicitly

Follow your retention process when replacing or withdrawing a document. Check how the connector handles missing or archived files; deleting an original may not immediately remove every indexed copy.

Keep formal document-control and approval processes in place. Vera helps people find information; it does not replace governance.

The backend has separate chat and archived-document retention controls. Automatic purge is disabled by default and requires an enabled, running execution path. Setting a retention period alone is not proof that deletion is occurring. The archived-document purge is not a blanket expiry rule for all active knowledge, and backup retention needs separate confirmation.