<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>vetting &amp;mdash; Katie&#39;s Notebook</title>
    <link>https://katie.madamgreen.xyz/tag:vetting</link>
    <description></description>
    <pubDate>Sat, 06 Jun 2026 04:25:15 +0000</pubDate>
    <item>
      <title>Survivor’s Guide: How to Set Boundaries &amp; Vet People</title>
      <link>https://katie.madamgreen.xyz/survivors-guide-how-to-set-boundaries-and-vet-people?pk_campaign=rss-feed</link>
      <description>&lt;![CDATA[Survivor’s Guide: How to Set Boundaries &amp; Vet People&#xA;&#xA;It’s easy to talk about boundaries. It’s another thing to live them—especially when you’re coming from a world that taught you to override your own instincts just to keep the peace. Here’s my lived, field-tested protocol for setting boundaries and vetting who gets close.&#xA;&#xA;Start With a “No” Default&#xA;&#xA;Assume your time, energy, and story are precious until proven otherwise. If you’re not sure, say no or say nothing. It’s always easier to open a door later than to slam it shut after a breach.&#xA;&#xA;Watch What People Do—Not Just What They Say&#xA;&#xA;Anyone can talk a good game about respect. I watch for whether people back off when I draw a line, respect my silences, and don’t fish for personal details I haven’t offered. If someone reacts poorly to a no, that tells me everything.&#xA;&#xA;Give Trust in Layers&#xA;&#xA;I don’t drop my whole story, location, or network to anyone on day one. I start with surface topics, then watch how people handle them. If they pass the first test, I add a little more. If they leak, boundary-push, or get weird, I cut it off—no explanation needed.&#xA;&#xA;Repair Privately, Not Publicly&#xA;&#xA;When there’s conflict, I handle repair in private, not for the audience or group chat. If someone can’t do real repair, or needs everything on display, that’s a sign to pull back.&#xA;&#xA;Use Tech to Back Up Boundaries&#xA;&#x9;•&#x9;Separate accounts for different groups or risk levels.&#xA;&#x9;•&#x9;Disappearing messages for sensitive topics.&#xA;&#x9;•&#x9;Don’t let people pressure you for your real name, address, or contact info.&#xA;&#xA;Vet Support Spaces, Too&#xA;&#xA;Not every “survivor” or “safe” space is actually safe. I watch for:&#xA;&#x9;•&#x9;Who runs the group, and what’s their reputation?&#xA;&#x9;•&#x9;Are there clear rules about privacy and leaks?&#xA;&#x9;•&#x9;Do people get called out for violating boundaries, or does drama get swept under the rug?&#xA;&#xA;Don’t Apologize for Protecting Yourself&#xA;&#xA;You never owe anyone more access than you want to give. If someone gets offended, that’s about their entitlement, not your safety.&#xA;&#xA;Take Breaks &amp; Audit Often&#xA;&#xA;I regularly review who has what access and adjust as needed. I don’t explain every change, and I don’t let guilt keep me in unsafe rooms.&#xA;&#xA;Remember: Your Network, Your Rules&#xA;&#xA;There’s no single right way to set boundaries, but you get to decide who has access, and when. Anyone who respects that is worth keeping. Anyone who doesn’t—cut the cord.&#xA;&#xA;#boundaries #survivor #fieldguide #consent #safety #vetting #support #protocols #railroad #memoir]]&gt;</description>
      <content:encoded><![CDATA[<p>Survivor’s Guide: How to Set Boundaries &amp; Vet People</p>

<p>It’s easy to talk about boundaries. It’s another thing to live them—especially when you’re coming from a world that taught you to override your own instincts just to keep the peace. Here’s my lived, field-tested protocol for setting boundaries and vetting who gets close.</p>

<p>Start With a “No” Default</p>

<p>Assume your time, energy, and story are precious until proven otherwise. If you’re not sure, say no or say nothing. It’s always easier to open a door later than to slam it shut after a breach.</p>

<p>Watch What People Do—Not Just What They Say</p>

<p>Anyone can talk a good game about respect. I watch for whether people back off when I draw a line, respect my silences, and don’t fish for personal details I haven’t offered. If someone reacts poorly to a no, that tells me everything.</p>

<p>Give Trust in Layers</p>

<p>I don’t drop my whole story, location, or network to anyone on day one. I start with surface topics, then watch how people handle them. If they pass the first test, I add a little more. If they leak, boundary-push, or get weird, I cut it off—no explanation needed.</p>

<p>Repair Privately, Not Publicly</p>

<p>When there’s conflict, I handle repair in private, not for the audience or group chat. If someone can’t do real repair, or needs everything on display, that’s a sign to pull back.</p>

<p>Use Tech to Back Up Boundaries
    •   Separate accounts for different groups or risk levels.
    •   Disappearing messages for sensitive topics.
    •   Don’t let people pressure you for your real name, address, or contact info.</p>

<p>Vet Support Spaces, Too</p>

<p>Not every “survivor” or “safe” space is actually safe. I watch for:
    •   Who runs the group, and what’s their reputation?
    •   Are there clear rules about privacy and leaks?
    •   Do people get called out for violating boundaries, or does drama get swept under the rug?</p>

<p>Don’t Apologize for Protecting Yourself</p>

<p>You never owe anyone more access than you want to give. If someone gets offended, that’s about their entitlement, not your safety.</p>

<p>Take Breaks &amp; Audit Often</p>

<p>I regularly review who has what access and adjust as needed. I don’t explain every change, and I don’t let guilt keep me in unsafe rooms.</p>

<p>Remember: Your Network, Your Rules</p>

<p>There’s no single right way to set boundaries, but you get to decide who has access, and when. Anyone who respects that is worth keeping. Anyone who doesn’t—cut the cord.</p>

<p><a href="https://katie.madamgreen.xyz/tag:boundaries" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">boundaries</span></a> <a href="https://katie.madamgreen.xyz/tag:survivor" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">survivor</span></a> <a href="https://katie.madamgreen.xyz/tag:fieldguide" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">fieldguide</span></a> <a href="https://katie.madamgreen.xyz/tag:consent" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">consent</span></a> <a href="https://katie.madamgreen.xyz/tag:safety" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">safety</span></a> <a href="https://katie.madamgreen.xyz/tag:vetting" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">vetting</span></a> <a href="https://katie.madamgreen.xyz/tag:support" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">support</span></a> <a href="https://katie.madamgreen.xyz/tag:protocols" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">protocols</span></a> <a href="https://katie.madamgreen.xyz/tag:railroad" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">railroad</span></a> <a href="https://katie.madamgreen.xyz/tag:memoir" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">memoir</span></a></p>
]]></content:encoded>
      <guid>https://katie.madamgreen.xyz/survivors-guide-how-to-set-boundaries-and-vet-people</guid>
      <pubDate>Wed, 12 Nov 2025 00:50:44 +0000</pubDate>
    </item>
  </channel>
</rss>