# Public Private Boundary Public Private Boundary is the rule for deciding what belongs in the public Mynd and what should stay private, clinical, relational, or operational. ## Meaning Joe's Mynd can be public without making Joe's whole life public. Public well-being boundary: ```text This is a public meaning and practice system. It is not therapy, diagnosis, or emergency support. Keep feedback public-safe. Use local crisis or emergency support when something is urgent. ``` The public graph should hold: - definitions - source-safe meaning - public paths - public practices - public questions - publish-safe maps of how the system works The public graph should not hold: - raw private reflections - private relationship details - client information - personal health data - private team operations - secrets, credentials, or access details - anything that belongs in a clinical system Use this rule: ```text If sharing it publicly would make the system clearer and would not expose private life, it may belong in the public Mynd. If sharing it publicly would expose private life, private care, private operations, or private trust, distill the meaning without copying the source. ``` Ten-second share check: ```text Can this be read by a stranger without exposing a private person, client, diagnosis, crisis, relationship, credential, or care record? If yes, share the small public signal. If no, distill the meaning and leave the source private. If you are unsure, do not share it publicly. ``` Use this simple split: | Signal type | Public Mynd action | |---|---| | A word is confusing | Share the word, page, and public-safe confusion. | | A practice helped or did not help | Share the practice, result, and no private story. | | A source taught something | Share the distilled meaning, not the private source. | | A person, client, diagnosis, crisis, relationship, credential, or care record is involved | Do not share publicly. Use a private or clinical system instead. | The public Mynd should show the meaning learned from life, not all the life that taught the meaning. Agents should follow [[For Agents]] and treat this note as a boundary. People should use [[Meaning Disagreement Flow]] or [[Did This Help]] without sharing sensitive details. The Brotherhood material should distinguish public care paths from private clinical or team operations. ## Source Of Meaning This note is grounded in Joe's need for Joe's Mynd to be public, useful, agent-readable, and safe enough to share with collaborators, readers, and The Brotherhood team. ## Relationship Over Time This boundary should become stricter before the system handles more personal, relational, or clinical data. If there is doubt, keep the source private and publish only the distilled meaning. ## Links - [[Use Joe's Mynd]] - [[For Agents]] - [[Start Here]] - [[Source Of Meaning]] - [[Meaning]] - [[Did This Help]] - [[Meaning Disagreement Flow]] - [[The Brotherhood]] - [[The Brotherhood Care Path]] - [[The Brotherhood Operating Meaning System]] ## Tensions The system needs enough public context to be useful and enough privacy to preserve trust. The public graph should feel honest without becoming exposing. ## Question What meaning can be shared without sharing what should stay private?