safety/private-public-split

To prevent private vault data from being exported unintentionally, you can apply an automatic classification step and export filter to keep private data private by default.

The best way to filter vault content for platform adapters or shared contexts is using an export filter combined with a privacy tagging protocol that requires user review and opt-in.

The privacy tagging protocol classifies data by marking vault entries with privacy labels, distinguishing between private and public-safe data to guide future exports and guardrails.

Yes, you can automatically classify vault entries as private or public-safe by tagging them with privacy labels and running an export to see what is allowed.

Shared context vault export requires privacy boundaries because inter-tool communications and platform exports can unintentionally expose private data without automatic classification and filtering guardrails.

Yes, you need to manually review vault entries during the export filtering process, as the privacy tagging protocol applies user review and opt-in to ensure private data remains protected.