Log every boundary test
After each boundary test, log what happened (who tested, how, what you did, how it felt) in an external system to build a dataset revealing patterns invisible from inside—which relationships produce most testing, which test types are hardest for you to withstand, whether your consistency is actually consistent.
When This Fires
- After every boundary test, regardless of outcome
- During boundary system reviews when assessing which boundaries need strengthening
- When you suspect inconsistent enforcement but can't prove it without data
- Complements Log every agent misfire with date, name, event… (failure log for agents) and Log every mistake for 30 days with date, event… (30-day error log) with the boundary-specific version
Common Failure Mode
Logging only failures: "I only need to track the times I caved." The successes are equally informative — they reveal what works, which test types you handle well, and which relationships respect boundaries after testing. A log of only failures produces a demoralization spiral rather than a balanced picture.
The Protocol
(1) After each boundary test, log four fields: Who: which person tested the boundary? How: what form did the test take? (Direct request, emotional appeal, authority invocation, going around you, guilt-tripping.) Response: what did you actually do? (Maintained, softened, capitulated, escalated.) Feeling: how did enforcement feel? (Confident, anxious, guilty, relieved, resentful.) (2) Keep the log simple — one line per test. The goal is consistency of logging, not depth of analysis. (3) Monthly: review the accumulated log. Look for patterns in who tests, how, when you succeed, and when you struggle. (4) Use patterns to strengthen the system: prepare for the test types you're most vulnerable to, address the relationships that test most frequently, and adjust boundaries that produce disproportionate emotional cost.