Boundary Breach Checklist (๐ & ๐_Tone Diagnostic)
1. Purpose
This guide implements the recommended โBoundary Breach Checklistโ for collaborators who experience high friction (๐_Tone) and need a simple way to trace the problem back to Boundary (๐) and Resonance (๐ก).
It is a quick WebKernel diagnostic, not a full protocol.
2. When to Use
Use this checklist when any of the following are true:
- you feel persistent frustration, overwhelm, or resentment around the work,
- conversations feel defensive or tense,
- tasks multiply faster than they resolve,
- collaborators seem confused about scope or expectations.
3. Step 1 โ Check ๐_Tone (Emotional Friction)
Answer YES/NO:
- Am I feeling rushed or cornered?
- Do I feel I โoweโ more than I can realistically give?
- Am I mentally rehearsing arguments or defenses?
- Do I feel shame, fear, or anger when I think about this work?
If 2 or more answers are YES, ๐_Tone is high.
High ๐_Tone is a signal, not a failure.
4. Step 2 โ Check ๐ (Boundary)
Ask:
- Have I explicitly defined my Boundary (time, money, scope, relationships) for this work?
- Have I said โyesโ to anything that violates that Boundary?
- Are there people depending on me who do not know my actual limits?
- Would I be embarrassed to say my real limits out loud?
If any answer is YES, assume a Boundary breach.
5. Step 3 โ Check ๐ก (Resonance / Fides)
Ask:
- Does this work still align with my deepest โwhy,โ or am I just going through motions?
- Am I avoiding an honest conversation about misalignment?
- Am I using PortusSophiaโข language to justify something that doesnโt feel right?
If any answer is YES, ๐ก is drifting.
6. Step 4 โ Decide the Next Move
Based on the checks:
- High ๐_Tone + Breached ๐:โ Invoke Recenter Protocol Pattern. :contentReference[oaicite:25]{index=25}
- Stable ๐ + Drifting ๐ก:โ Schedule a Stewardship conversation (Daniel + Sara) to clarify alignment.
- High ๐_Tone + unclear ๐ + unclear ๐ก: โ Stop committing to new work, write a one-page Recenter declaration.
7. Steward & Tool Integration
- Sara can include this checklist in onboarding and guidance docs.
- PortusKernelโข tools can implement it as a lightweight questionnaire.
- Draco can use aggregated Boundary Breach signals to identify systemic risk patterns.
Principium: Memoria Corporalis