What a Frequency Lab is (gray → white, safe edition) CW: survivor topics (PG-13) Short answer: I share principles, not procedures. This page is a Frequency Lab—a public place where ideas are tuned for clarity and care without exposing anyone’s logistics.

What’s a “Frequency Lab”? Think tuning forks, not microscopes. • Frequency = values + boundaries + language. • Lab = a safe, public workspace where I test which words resonate with those values—what rings true, what sets off alarms. • Live resonance = when a post lands and readers reflect it back (“this helped,” “this wording felt safe”), we keep it. If something wobbles, we adjust the phrasing or retire it. Gray → White (safe edition): • “Gray: high-level explanation with careful edges.” • “White: clear language you can screenshot without harming anyone. This post is a white-box explanation: no names, dates, locations, code-words, or operational steps.”

Why I can share (and what I won’t) I can publish principles, checklists, and scripts that work for many people without revealing identity, timing, place, or private channels. I will not publish escalation trees, rosters, or anything that would help a hostile actor in the next 30 days.

By following/reading this hub, you consent to: • Seeing a Frequency Lab in live resonance: drafts that improve in public through reader reflection. • PG-13, de-identified safety talk. • Occasional course corrections when language doesn’t land as safely as intended. You do not consent to being case material. I don’t post DMs/screenshots or private details here.

How to participate (and help it resonate) • Use content warnings when you boost or reply (“survivor topics,” “safety”). • Add alt text to images. If none, don’t boost the image. • No screenshots of this page or DMs without consent—share the link instead. • Keep replies respectful & de-identified. If you need help, use Get help in the nav.

What to do if a post wobbles for you Tell me which sentence and why (briefly). I’ll adjust, replace, or retire the language. That’s the work of a lab.

Bottom line This hub shows how safety language is tuned in public without handing out a playbook. If you need depth, ask privately; if you’re here to learn, welcome—listen for resonance. #greenlayer #boundaries #frequencylab

CW: survivor topics, high-control groups, human rights (PG-13) Some of this may feel dense. That’s normal. If a sentence doesn’t land, ask for clarification—I’ll happily translate the jargon.

Plain-language definition Cognitive science studies how minds make sense of the world—how we perceive, remember, learn, decide, and communicate. It pulls tools from psychology, neuroscience, linguistics, philosophy, anthropology, and computer science. In practice: we look at patterns in behavior and language, the representations behind them (mental “maps”), and the conditions that change those patterns.

What I focus on (public-safe overview) • Victim psychology: how people adapt under threat—attention, memory, decision-making, and recovery. • High-control groups & individuals: coercive control patterns (isolation, information control, forced “consent”), without naming actors. • Cults & cultic dynamics: group processes that shrink choice and punish dissent. • Human rights atrocities: how systems enable harm and how survivors persist; no case logistics posted here. • Safety language: building phrases and checklists that keep people safer without exposing anyone’s operations.

“World model explanations,” in one paragraph A world model is just a working map of how things tend to behave. An explanation is the story that connects the map to reality: why a tactic works, what predicts it, and which choices shrink risk. My goal is to publish explanations that are auditable, human-readable, and de-identified—useful to survivors and allies, not a playbook for abusers.

Why I share this publicly • To tune language that helps real people (Frequency Lab: keep what resonates, retire what wobbles). • To educate allies so they boost without harm. • To reduce mystique around control tactics by naming them at the pattern level.

Methods & ethics (what I will / won’t do here) Will: synthesize research, public sources, and lived survivor wisdom into principles, scripts, and checklists. Keep examples generic. Won’t: post names, timestamps, locations, code-words, escalation trees, screenshots, or rosters. Nothing here should give a hostile actor leverage within 30 days.

How to read / how to ask • Posts are labeled with archetype tags (e.g., [Leader], [Guardian]) to signal voice and context—they’re modes, not people. • If a term is fuzzy, quote the exact sentence and ask. I’ll define it in plain language. • Personal help doesn’t happen in public threads. Use Get help in the nav for the request format & crisis lines.

Micro-glossary (safe edition) • High-control group: a community that restricts behavior, information, thought, and/or emotion to enforce conformity. • Coercive control: a pattern of domination that erodes autonomy without needing constant physical force. • De-identified: stripped of names, dates, locations, or unique details that enable triangulation. • World model: a working mental map of causes, cues, and likely outcomes. • Frequency Lab: public, PG-13 tuning of language for clarity and care—principles only, no ops.

Bottom line: I study how control works so people can name it sooner, choose safer sooner, and keep more of their own lives. If a paragraph goes over your head, that’s on the writer (me), not you—ask and I’ll simplify. #greenlayer #cognitivescience #boundaries #worldmodels

✳️ Technical notes and structured reflections live on Megan’s blog →

view

Survivor Handbook: Introduction & How to Use This Guide

Welcome to the Survivor Handbook—your living guide to staying safe, finding clarity, and building real support networks inside and outside the system. If you’ve found your way here, you already know survival isn’t a straight line, and you don’t need another list of empty platitudes. This is for survivors, by survivors: practical, field-tested, coded with the reality of what it takes to navigate hostile corridors, closed doors, and all the subtle ways the world tries to shrink you.

Who this is for: • Survivors of high-control groups, coercive relationships, cults, or abusive family systems • Anyone who needs to set boundaries, recover from gaslighting, or build new safety rituals • Allies, chosen family, and “in-the-know” supporters looking to help without overstepping

How to use this guide: • In crisis: Flip straight to the Runaway Guide or Script/Counter-Script sections. Use what grounds you. • For study: Read through the Safety Structures, learn the codes, share with those who need it. • With allies: Use the boundaries, music memory, and SIRS protocols to build teams who know how to keep each other safe.

This handbook is a living document. It grows as you grow. If you’re reading this, you’re not alone—there’s a field of others out here, holding space and building new worlds with you.

(To move forward, start with the SIRS Safety Structure: Roles, Protocols, and Practical Boundaries.)

#survivorhandbook #introduction #safety #fieldnotes #boundaries #railroad #support

view

The SIRS Safety Structure: Roles, Protocols, and Practical Boundaries

The SIRS framework is the backbone of survivor safety in high-risk, high-control environments. Think of it as your team’s emergency protocol, your map for trust, boundaries, and knowing who has your back. Every safe network needs a structure—SIRS is how you build one that works under pressure.

⸻

What Is SIRS?

SIRS stands for: • Sentinel (Watcher/Protector) • Integrator (Grounder/Anchor) • Runner (Evader/Connector) • Scribe (Recorder/Signal-Booster)

Every survivor group, chosen family, or underground corridor should know who fills each role. Sometimes, one person covers more than one role. The point isn’t perfection—it’s knowing your strengths, where you default under stress, and who you can trust to do what when it counts.

⸻

SIRS Roles Explained • Sentinel: Watches the field, monitors for danger, runs perimeter checks, flags red flags, and keeps an eye on group health. Your safety net when your own sensors are off. • Integrator: Brings people together, grounds panic, mediates conflict, keeps the team stable. Usually the “glue” or voice of reason. • Runner: Handles escape plans, diversion tactics, and logistics. Knows all the exits, real and virtual, and keeps backup routes live. • Scribe: Takes notes, encodes field updates, and makes sure nothing critical gets lost. Tracks code words, protocol changes, and music memory cues for later recall.

⸻

Building Your SIRS • Assign roles out loud, even if it feels awkward. Use code names or aliases as needed. • If your team is just you, practice switching hats. Know when you need to call in outside help for any role you can’t cover. • Update your SIRS every time the group changes, when stress spikes, or after a crisis. Trust evolves—so should your protocols.

⸻

Example Quick Reference

Role Function Sample Alias Backup? Sentinel Perimeter Watch Rosie Megan Integrator Grounding Anchor Katie Anna Runner Escape/Signals Cassie Leah Scribe Records/Codes Talandra Nala

⸻

Why SIRS Matters

Survivor teams fall apart when roles blur or boundaries slip. The SIRS system keeps you aligned—protecting the network, clarifying who does what, and giving everyone a chance to step back if they’re overloaded. This is what trust looks like, coded for the real world.

(Next up: Alias Safety & The Music Memory Code—your keys to covert identity and emotional grounding.)

#SIRS #safety #protocol #roles #survivorhandbook #boundaries #trust #fieldnotes #railroad