One file can change several souls
An edit in one soul vault usually affects that soul's next boot. Principles and libraries in a shared vault may be inherited by several souls. One wrong sentence can bend an entire family's tool behavior and memory policy.
Risk therefore cannot be measured only by deletion. A small non-destructive edit with a broad blast radius is destructive-ish. Confirmation strength should follow how many future judgments receive the change, not its character count.
Use the strongest ceremony
A shared edit should present target, before and after, affected consumers, and actor identity together, followed by an armed confirmation. The first action prepares intent; the second confirms the exact object and change.
Longer warning prose is not enough. If the user can approve without reading the diff, ceremony is merely friction. Narrow the change and expose expected token and index effects.
Shared is also a single source
Copying common rules into each soul vault turns edit blast radius into silent drift. Some souls read new guidance while others inherit old copies. One shared source with rebuildable projections is safer.
Yet shared must not become a universal vault. Common contracts belong there; identity and private memory remain per soul. Sharing is justified by common ownership of meaning, not merely by multiple consumers.
Think of correction at family scale
Fixing only one consumer after a bad shared change splits the family. Read historical evidence, apply a forward correction to shared source, and prove every consumer observed the new revision.
If runtime caches exist, invalidation belongs to the protocol. A successful source commit with one long-lived process holding old rules is only half a landing.