Profile. Optional names for each person. Used as labels throughout the app. Leave blank to use Person A and Person B.
Names
Right Now — Two taps to the right tool for what’s happening at this moment. No browsing required.
What's happening right now?
We're in conflict or just had friction
One or both of us is overloaded
Communication keeps missing
A task or household thing fell apart
I need to regulate right now — just me
🔥 We're in conflict or just had friction
In the middle of it right now
Just ended but still unresolved
Same fight keeps recurring
🪫 One or both of us is overloaded
Right now, capacity is very low
Stress from outside is spilling in
Nothing is working, all tools feel hard
💬 Communication keeps missing
Intent is clear but it's landing wrong
One of us is fast, the other needs time
We don't know if a conversation is done
📋 A task or household thing fell apart
Task didn't happen, consequences loom
"I thought you had that" keeps happening
Need to renegotiate the whole system
Recommended tool
Time-Out With Return Plan
Call the pause first. Return plan keeps it from becoming abandonment.
Recommended tool
After-Conflict Debrief
Orientation without reopening. 10 minutes, no trial.
Recommended tool
Early Warning Signs
Map the buildup so the pattern becomes visible before the peak.
Recommended tool
Capacity Snapshot
Rate it, name the constraint, pick one support action. 3 minutes.
Recommended tool
External Stress Containment
Name the source so it stops being read as relational.
Recommended tool
Capacity Reset
Suspend nonessential interaction. Focus on rest and basics only.
Recommended tool
Direct vs. Inferred Meaning Check
Speaker states literal meaning; listener states what they inferred.
Recommended tool
Processing-Speed Bridge
1 minute. Identify mode. Use the bridge phrase.
Recommended tool
End the Exchange Cleanly
State what was resolved or parked. Explicitly close.
Recommended tool
Execution Repair
Start with the miss, not the person. One repair action forward.
Recommended tool
Task Ownership Lock
One task, one owner, clear done state.
Recommended tool
Renegotiation Scripts
Six ready scripts for opening the conversation without conflict.
🌊 I need to regulate right now — just me
I’m overwhelmed and overstimulated
I’m flooded — I can’t think clearly
I need to check my capacity before engaging
Recommended tool
4.7 Overload Signals
Your personal overload signals and what helps quickly. Go straight to your section.
Recommended tool
4.6 Drain/Restore
Find one restore action from your column. That’s the only decision you need right now.
Recommended tool
1.3 Capacity Snapshot
Rate it and name the constraint. 3 minutes. Then you know what you’re working with.
All tools at a glance. Highlighted cells have saved content. Tap any cell to go directly to that tool.
Shared Map
1.1
Mini-Glossary
Not started
1.2
Signal Map
Not started
1.3
Capacity
Not started
1.4
Agreements
Not started
1.5
Repair Ritual
Not started
1.6
EF Map
Not started
Communication
2.1
Literal Ask
Not started
2.2
Processing Bridge
Not started
2.3
Meaning Check
Not started
2.4
Channel Match
Not started
2.5
Clean Close
Not started
2.6
Translation
Not started
Conflict
3.1
Early Warning
Not started
3.2
Time-Out
Not started
3.3
De-Escalation
Not started
3.4
After-Conflict
Not started
3.5
Repair Scripts
Not started
Regulation
4.1
Escalation Catch
Not started
4.2
Regulation Plan
Not started
4.3
Load Limit
Not started
4.4
Stress Contain
Not started
4.5
Capacity Reset
Not started
4.6
Drain/Restore
Not started
Sleep & Recovery<
Map
Sleep Map
Not started
Negotiate
Negotiation
Not started
Design
Design
Not started
Renegotiate
Renegotiate
Not started
Coordination
5.1
Task Lock
Not started
5.2
Affection Map
Not started
5.3
Date Builder
Not started
5.4
Appreciation
Not started
5.5
Exec. Repair
Not started
5.6
Scripts
Not started
5.7
Labor Inventory
Not started
History — Every save and progress note is stored here with a timestamp. Tap any entry to go back to that tool.
No saves yet. Complete any tool and your history will appear here.
Weekly rhythm tool. Each day, rate your available capacity and total demand. When demand exceeds capacity, that is information about mismatch — not failure. Use the end-of-week summary to spot patterns and name one adjustment.
High demand is not a personal failure. It is a signal about mismatch between your nervous system and your environment.
This week
Monday
Capacity (0–10)
—
Demand (0–10)
—
Sleep quality last night (0–10)
Notes / what helped
Tuesday
Capacity (0–10)
—
Demand (0–10)
—
Sleep quality last night (0–10)
Notes / what helped
Wednesday
Capacity (0–10)
—
Demand (0–10)
—
Sleep quality last night (0–10)
Notes / what helped
Thursday
Capacity (0–10)
—
Demand (0–10)
—
Sleep quality last night (0–10)
Notes / what helped
Friday
Capacity (0–10)
—
Demand (0–10)
—
Sleep quality last night (0–10)
Notes / what helped
Saturday
Capacity (0–10)
—
Demand (0–10)
—
Sleep quality last night (0–10)
Notes / what helped
Sunday
Capacity (0–10)
—
Demand (0–10)
—
Sleep quality last night (0–10)
Notes / what helped
Weekly Summary
Most common demand drivers this week
Early warning signs that appeared repeatedly
Highest-demand day and what made it different
What actually helped most this week
One adjustment to try next week
Related tools
1.3 Capacity Snapshot4.5 Capacity ResetAssess: CRMAssess: CBR-SM
Weekly overload log. Rate each day, check what contributed, note what you noticed early and what helped. Overload follows patterns. This log makes those patterns visible so you can move from reacting to preventing.
This week
This Week
Monday
Overload level (0–10)
Main contributorsEarly signs I noticed
What helped (or didn't)
Tuesday
Overload level (0–10)
Main contributorsEarly signs I noticed
What helped (or didn't)
Wednesday
Overload level (0–10)
Main contributorsEarly signs I noticed
What helped (or didn't)
Thursday
Overload level (0–10)
Main contributorsEarly signs I noticed
What helped (or didn't)
Friday
Overload level (0–10)
Main contributorsEarly signs I noticed
What helped (or didn't)
Saturday
Overload level (0–10)
Main contributorsEarly signs I noticed
What helped (or didn't)
Sunday
Overload level (0–10)
Main contributorsEarly signs I noticed
What helped (or didn't)
Weekly Pattern Summary
Most common overload contributors this week
Earliest warning signs that appeared repeatedly
Highest overload day and what made it different
What actually helped most this week
One prevention strategy to try next week
Related tools
4.7 Overload Signals1.3 Capacity4.4 Stress ContainmentAssess: CBR-SM
Your pinned tools. Pin up to 4 tools you use most often. Each tool has a pin button at the top. Pinned tools appear here for one-tap access.
⚠ Maximum 4 tools pinned. Unpin one to add another.
Pin a tool by tapping the “Pin this tool” button at the top of any tool page.
Monthly maintenance check-in. For when things are going okay and you want to keep it that way. 15 minutes together. Each month saves separately so you build a record over time.
Use when things are stable. If something is in crisis, go to Right Now instead.
This month
How Are We Doing
Communication
Are we understanding each other and following through?
Working well
Drifting
Conflict & repair
Are repairs holding? Are we catching things early?
Working well
Drifting
Capacity & load
Is load distributed sustainably? Are we tracking capacity?
Working well
Drifting
Sleep & environment
Is the sleep system working? Is the environment manageable?
Working well
Drifting
Coordination
Are tasks getting done without reminders or resentment?
Working well
Drifting
Connection
Are we spending time together that actually restores us?
Working well
Drifting
What We Want to Protect
What is working so well we want to deliberately protect it?
One Adjustment
One drifting area. One adjustment. Two weeks before anything else changes.
The one thing we're adjusting
Next check-in date
Looking Back
Fill this in at the start of the next check-in before moving to the new month.
Did the adjustment from last check-in hold?
What changed because we checked in?
Related tools
Weekly Planner1.4 Working Agreements1.3 Capacity
Use when you keep having the same misunderstanding with different wording, or you agree in the moment and realize later you meant different things. Complete at least 3 entries and return to add more.
1
Write the word or phrase that keeps causing confusion.
2
Each person writes what they actually mean by it — practical, not ideal.
3
Agree on one shared definition and a clearer phrase to use instead.
Done looks likeAt least 3 shared definitions with one alternative phrase each.
Our Glossary
1.
Word or phrase
Person A — what I actually mean
Person B — what I actually mean
Our shared definition
Example in our relationship
Better phrase to use
2.
Word or phrase
Person A — what I actually mean
Person B — what I actually mean
Our shared definition
Example in our relationship
Better phrase to use
3.
Word or phrase
Person A — what I actually mean
Person B — what I actually mean
Our shared definition
Example in our relationship
Better phrase to use
4.
Word or phrase
Person A — what I actually mean
Person B — what I actually mean
Our shared definition
Example in our relationship
Better phrase to use
Quick Add-On
When we notice confusion, we will say:
Pause phrase“Pause — what do you mean by ___ ?”
Glossary check phrase“In our glossary, ___ means ___. Is that what you mean right now?”
Use when you misread each other’s cues — silence, short replies, shutting down, fast talking — and assume intent that escalates. Map 3–5 cues each.
1
Each person fills in their own section independently. Write what’s usually true, not the ideal version.
2
Read each other’s maps without debating. The map is the map.
3
Agree on one shared rule at the bottom. Try it for two weeks before adjusting.
Done looks likeEach person has at least 3 cues mapped with a first-response plan.
Person A — My Cues
1.
My cue (what you notice)
What it usually means for me
What makes it worse
What helps
Best response from you (try this first)
2.
My cue (what you notice)
What it usually means for me
What makes it worse
What helps
Best response from you (try this first)
3.
My cue (what you notice)
What it usually means for me
What makes it worse
What helps
Best response from you (try this first)
4.
My cue (what you notice)
What it usually means for me
What makes it worse
What helps
Best response from you (try this first)
Person B — My Cues
1.
My cue (what you notice)
What it usually means for me
What makes it worse
What helps
Best response from you (try this first)
2.
My cue (what you notice)
What it usually means for me
What makes it worse
What helps
Best response from you (try this first)
3.
My cue (what you notice)
What it usually means for me
What makes it worse
What helps
Best response from you (try this first)
One Shared Rule
When we see a cue, we will try the “best response” before asking follow-up questions.Write the specific version that works for your relationship. Try it for 2 weeks before changing it.
Use daily as needed — especially when small things are becoming big, you don’t know whether to talk now or wait, or one of you needs support and the other needs to know what kind. Takes 3 minutes.
1
Each person rates their capacity right now (0–10). If either person is 0–4, Low-Capacity House Rules activate automatically.
2
Each person picks their top constraint and one support action.
3
You both now know what today can handle and what gets postponed.
Capacity Right Now
Person A
Depleted (0)Full (10)
Person B
Depleted (0)Full (10)
Today’s Top Constraint
Choose one each
Low-Capacity House Rules
Activate automatically when either person rates 0–4.
Support + Protection
Person A — what helps me right now
Person B — what helps me right now
Shared Signal
Our shared signal for low capacityA phrase or text either person can send. When it appears, House Rules activate without discussion.
Use when you keep relitigating the basics. Choose the categories you need and keep the total to 5–8 agreements. Write them as observable actions.
1
Choose the categories that matter most right now. Leave the rest blank.
2
Write agreements as what you will do. Add one repair step for the agreements most likely to break.
3
Run for 2 weeks, then move anything to Keep or Change.
Done looks like5–8 agreements with repair steps.
Our Working Agreements
Interruptions / talking over
Our agreement
If this breaks — quick repair
Timing — when we talk
Our agreement
If this breaks — quick repair
Processing time — pauses & thinking
Our agreement
If this breaks — quick repair
Tone / volume
Our agreement
If this breaks — quick repair
Touch / space
Our agreement
If this breaks — quick repair
Transitions — starting / stopping tasks
Our agreement
If this breaks — quick repair
Asking for help
Our agreement
If this breaks — quick repair
Conflict rules — what we will not do
Our agreement
If this breaks — quick repair
Keep / Change Later
Keep
Change
Use when you feel the shift — tension, distance, sharpness, shutdown, tone, transitions — and want to reset without a full processing conversation. Fill this in together ahead of time.
Done looks likeYou’re calmer and both know what happens next.
Our Reset Call Phrase
The phrase either person can say or text to call the resetShort. Neutral. Agreed before you need it.
The Steps
Step 1 · Pause (10–20 seconds)
Choose your pause action
Step 2 · Name the Moment (one sentence each, no debate)
Person A — I’m noticing…
Person B — I’m noticing…
Step 3 · Impact + Ownership (one sentence each)
Person A — That likely landed as ___ . I own ___.
Person B — That likely landed as ___ . I own ___.
Step 4 · One Need (right now)
Each person picks one
Next Action
Choose one
Quick reconnect action (optional)
If either person can’t do the ritual right nowWrite the fallback before you need it.
A note: The ritual works because it’s short and pre-agreed. Goal is regulation, not resolution.
Use when tasks keep clashing or one person ends up compensating for the other's executive function gaps. Complete separately (10 min each), then compare without discussing solutions yet.
Done looks likeAt least one EF gap named and one practical support that doesn't rely on the other person changing.
Person A
| Function | I struggle to… | It helps me to… |
|---|---|---|
| PLANNING | ||
| ATTENTION | ||
| SELF-MONITORING | ||
| TASK INITIATION | ||
| TASK COMPLETION | ||
| COGNITIVE FLEXIBILITY | ||
| WORKING MEMORY |
Person B
| Function | I struggle to… | It helps me to… |
|---|---|---|
| PLANNING | ||
| ATTENTION | ||
| SELF-MONITORING | ||
| TASK INITIATION | ||
| TASK COMPLETION | ||
| COGNITIVE FLEXIBILITY | ||
| WORKING MEMORY |
Discuss & Plan
How do our unchecked needs clash when solving tasks together?
What practical support or reminders can we make room for?
What systems give vs. just exhaust?
We use stretch supports to complement each other's skills.
Related tools
5.1 Task Ownership Lock5.6 Renegotiation ScriptsGuide: Invisible Labor
Use when a message feels emotionally loaded but unclear, or you don’t know whether to respond, act, or wait. Remove tone, context, and history. Identify only whether an explicit action is being requested.
Done looks likeYou know whether to act, clarify, or pause.
Workspace
Message as received
Explicit action requested (if any)
My response
Response text (if needed)
If no action is requested — no response is required yet.
Use when one partner responds immediately and the other needs time, silence is read as avoidance, or pressure builds because timing isn’t coordinated. Identify which mode is active right now, use the matching phrase.
Done looks likeTime differences stop being misinterpreted.
Workspace
Current processing mode
Bridge phrase
I’ve received this and need time. I’ll respond by:
If I need acknowledgment now (not a solution), I’ll say:
Use when one partner speaks directly and the other infers subtext, neutral statements trigger defensive reactions, or “That’s not what I meant” keeps happening. Speaker states literal meaning; listener states what they inferred; adjust before responding.
Done looks likeYou’re responding to the same meaning.
Workspace
Literal meaning
Inferred meaning
Corrected understanding
Use when one partner prefers text and the other needs voice, text is increasing misunderstanding, or switching channels causes friction. Identify the current channel, decide if it fits the content, and switch explicitly.
Done looks likeThe channel fits the message.
Workspace
Current channel
Best channel for this message
Transition phrase“This needs ___ instead. Let’s do that at ___.”
Use when conversations taper without closure, one partner thinks it’s done and the other doesn’t, or issues keep resurfacing unintentionally. State what was resolved or parked, state whether follow-up is needed, then explicitly close.
Done looks likeBoth partners know whether this is finished.
Workspace
Status
Follow-up (if any)
Closing line
Use as a reference when intent keeps getting lost. The table is pre-filled with the most common mixed-neurotype translation failures. Write your own specific versions below.
What I Mean vs. What You Hear
One-Sentence Scripts — Person A
When I i go quietIt means ___ / It does not mean ___
When I i interruptIt means ___ / It does not mean ___
When I i ask for clarityIt means ___ / It does not mean ___
When I i avoid the conversationIt means ___ / It does not mean ___
When I i push for resolutionIt means ___ / It does not mean ___
One-Sentence Scripts — Person B
When I i go quietIt means ___ / It does not mean ___
When I i interruptIt means ___ / It does not mean ___
When I i ask for clarityIt means ___ / It does not mean ___
When I i avoid the conversationIt means ___ / It does not mean ___
When I i push for resolutionIt means ___ / It does not mean ___
Related tools
1.2 Signal Map2.3 Meaning CheckGuide: State Decoder
Use when conflicts feel like they come out of nowhere, or by the time you notice tension it’s already too intense. Each person maps early signs that conflict is building, what makes it worse, and one containment move to use immediately.
Done looks likeYou recognize escalation earlier and respond before it peaks.
Person A — My Early Warning Signs
Early sign I show
What makes it worse
What helps
Containment move we’ll use
Person B — My Early Warning Signs
Early sign I show
What makes it worse
What helps
Containment move we’ll use
Shared Rule
When we notice a yellow flag, we shift to containment — not problem-solving.Write the specific version of this rule that fits your relationship.
Use when arguments spiral out of control, one of you needs time to re-regulate, or leaving the conversation increases fear or chasing. Either person calls the time-out using the agreed phrase, states how long, and states when and how they will return.
Done looks likeNo one wonders whether the relationship is at risk.
Workspace
Our time-out phrase
Length of pause (choose one)
What we do during the pause
If someone can’t return as planned“I need more time. I can return at ___.”
Use when calming strategies are mismatched — what helps Person A makes things worse for Person B. Each person picks 1–2 things that help them when escalated. Agree to try the “helps” before anything else.
Done looks likeFewer accidental escalations.
Workspace
Person A — when I’m escalated, this helps (pick 1–2)
Person B — when I’m escalated, avoid these (pick 1–2)
Shared agreementWe try the “helps” before anything else.
Use when a conflict ended but still feels unresolved, or you want learning without reopening the argument. 10 minutes, no trial. Each person calls a brief check-in to orient — not to reopen.
Done looks likeYou feel oriented, not reopened.
Workspace
Person A — what helps me debrief (pick 1–2)
Person B — what to avoid during debrief (pick 1–2)
What we learned from this oneOne sentence each. No debate. Just the signal, not the analysis.
Use when apologies turn into explanations, repair attempts feel empty or defensive, or you want reconnection without rehashing. Keep it short. Stop talking after the script.
Done looks likeThe other person feels acknowledged.
Repair Script
Script
That landed as…
I own…
Next, I will…
Response options (the receiving person picks one)
Use when tone shifts quickly, small issues suddenly feel big, or you recognize the pattern before damage happens. Agree on a neutral escalation signal in advance. Either partner uses it at the first sign of escalation. The signal is never debated; calling it is not an accusation.
Done looks likeEscalation halts before harm occurs.
Workspace
Escalation signal & immediate regulation action
Our escalation signal
Immediate regulation action
Use when one partner needs space and the other needs reassurance, or attempts to help make things worse. Space ≠ rejection. Contact ≠ control. Regulation comes before discussion. Each partner identifies what helps them regulate, then set a structure that allows both to occur safely.
Done looks likeBoth partners feel safer, even if apart.
Workspace
Regulation plan
Partner A needs
Partner B needs
Reconnection time or signal
Use when discussions derail halfway through, someone shuts down or becomes reactive, or “We were fine and then it wasn’t.” Agree on a time or topic limit before starting. Stop when the limit is reached. Stopping does not mean avoidance.
Done looks likeConversation ends without collapse.
Workspace
Conversation limit
Conversation limit (time or topic)
Resume plan (if needed)
Use when work, health, family, or life stress spills into interactions, or irritability is misattributed to the relationship. Name the external stress source. Stress origin is named, not blamed. Capacity is not character.
Done looks likeStress feels contextualized, not relational.
Workspace
External stress containment
External stress source
Temporary adjustments
Review date
Use when nothing is working, all tools feel hard, or even neutral interaction is strained. Capacity limits are real. Reset is not quitting. Recovery enables future connection. Name that capacity is low, suspend nonessential interaction, focus on rest and basics.
Done looks likeCapacity begins to return.
Workspace
Capacity reset
Signals of low capacity (what we’re each noticing)
Paused expectations (for now)
Recovery focus
Use when you need to make your nervous system’s drain and restore patterns visible to your partner — and to yourself. Each person fills in their own columns. Compare, note what you didn’t know, and use the discussion prompts to adjust.
Done looks likeEach person has a visible drain and restore profile. One thing adjusts in the next week based on what you both learned.
Person A
Drains Me
Restores Me
Person B
Drains Me
Restores Me
Discuss to Balance
What drain left you most exhausted lately?
Which restore did you delay or skip recently?
Where are we light / heavy, and how can we adjust?
We restore to self-regulate — not to normalize getting drained.
Related tools
4.2 Regulation Plan
4.5 Capacity Reset
1.3 Capacity Snapshot
Guide: Capacity
Fill out once. Return to it when something feels off but you can't name it yet. Check the common signals as starting points, add your own, and note what helps before things escalate. This card is for each person to complete separately. When you spot a signal, go straight to the "What Helps" column — don't wait to feel worse.
Done looks likeEach person has their early signals identified in at least two domains, with at least one personal signal and one personal help strategy added.
Person A — My Overload Signals
Person B — My Overload Signals
Related tools
Weekly Overload Tracker4.1 Escalation Catch4.8 Context Load3.1 Early Warning Signs
Maps eight domains of load your nervous system is currently managing. Rate where you are right now — not your best or worst day. Use this periodically (weekly or when something feels heavy) to see which domains are carrying the most weight and whether load is shifting over time. Each person completes their own section.
0 = no load in this domain right now | 10 = extreme load
Person A — Current Load
Person A — the domain carrying the most weight right now
Person A — one thing that could reduce load this week
Person B — Current Load
Person B — the domain carrying the most weight right now
Person B — one thing that could reduce load this week
Compare
Where are our loads overlapping right now?
One thing we can adjust to reduce the heaviest domain for either person
Related tools
4.7 Overload Signals4.4 Stress ContainmentWeekly PlannerAssess: SEFM
Maps current reserves across seven life domains. Rate where you are right now — not where you wish you were. Use periodically (monthly or when things feel stuck) to see whether reserves are building or depleting over time. Complete separately. Compare where your depletion zones overlap.
0 = this reserve is completely empty right now | 10 = well-resourced in this area
Person A — Current Reserves
Social Support
Quality and availability of connection, community, and safe relationships
Close friendships, family connection, community belonging, trusted people to turn to
—
Financial Security
Current sense of stability around income, savings, and material resources
Stable income, manageable debt, emergency savings, access to healthcare
—
Physical Health
How well your body's basic needs are being met
Consistent sleep, regular movement, manageable pain, adequate nutrition
—
Emotional Regulation
Current access to tools and support for managing emotional responses
Coping tools that work, ability to name and process feelings, co-regulation support
—
Environmental Safety
Degree to which your physical surroundings feel stable and under your control
Stable housing, sensory-friendly spaces, predictable routines
—
Time & Rest
How much unstructured time and genuine recovery you currently have access to
Free time, rest without guilt, boundaries on obligations, buffer in your schedule
—
Meaning & Purpose
Current sense of alignment between your daily life and your values
Work that matters, creative expression, contribution to others, sense of direction
—
Strongest areas are your current anchors — protect them. Lowest areas are your depletion zones — prioritize replenishment here.
My strongest reserves right now (anchors)
My most depleted reserves right now
One thing that could rebuild my lowest reserve
Person B — Current Reserves
Social Support
Quality and availability of connection, community, and safe relationships
Close friendships, family connection, community belonging, trusted people to turn to
—
Financial Security
Current sense of stability around income, savings, and material resources
Stable income, manageable debt, emergency savings, access to healthcare
—
Physical Health
How well your body's basic needs are being met
Consistent sleep, regular movement, manageable pain, adequate nutrition
—
Emotional Regulation
Current access to tools and support for managing emotional responses
Coping tools that work, ability to name and process feelings, co-regulation support
—
Environmental Safety
Degree to which your physical surroundings feel stable and under your control
Stable housing, sensory-friendly spaces, predictable routines
—
Time & Rest
How much unstructured time and genuine recovery you currently have access to
Free time, rest without guilt, boundaries on obligations, buffer in your schedule
—
Meaning & Purpose
Current sense of alignment between your daily life and your values
Work that matters, creative expression, contribution to others, sense of direction
—
Strongest areas are your current anchors — protect them. Lowest areas are your depletion zones — prioritize replenishment here.
My strongest reserves right now (anchors)
My most depleted reserves right now
One thing that could rebuild my lowest reserve
Compare & Plan
Where are our depleted reserves overlapping?
What can we protect together right now?
One rebuild step we can make room for this week
Related tools
4.8 Context Load4.5 Capacity ResetWeekly PlannerGuide: Capacity
Sleep is the single strongest predictor of same-day capacity. In mixed-neurotype relationships, sleep environments, chronotypes, and wind-down needs often differ significantly. This section maps those differences, negotiates workable agreements, and designs a sleep system that reflects what both people actually need — not an assumed shared default.
This section does not assume co-sleeping or any particular relationship structure. Mapping covers whether a shared or individual wind-down is wanted and workable. Design builds whatever the negotiation actually produces.
How to Use This Section
1
Map — each person fills in their own profile independently. Honest over ideal.
2
Negotiate — compare maps, identify overlaps and conflicts, agree on what's non-negotiable for each person.
3
Design — build the actual sleep system from the negotiation output. Shared environment, individual or shared wind-down, morning ramp-up, and a low-capacity protocol.
4
Renegotiate & Redesign — return when something stops working. Not a full redo. One adjustment at a time.
Where to Start
Starting fresh or never mapped this before → Start with Mapping
Maps done, ready to negotiate → Go to Negotiation
Negotiation done, building the system → Go to Design
Something stopped working, needs adjustment → Go to Renegotiate
Complete independently. Fill in your own section without reference to your partner's answers. The goal is honest self-knowledge, not compromise or anticipating what the other person needs.
Done looks likeBoth people have filled in all four domains. Wind-down mode preference is clearly stated for each person. Sleep debt signals are identified.
Person A — Sleep Map
Person A
Sensory Environment
Light while sleeping
Sound while sleeping
Temperature preference
Touch / proximity while sleeping
Bedding / texture needs
Other sensory needs not listed
Chronotype
Natural sleep time (when you actually get tired)
Natural wake time (without an alarm)
How hard is waking up for you
When your cognitive energy peaks
Anything else about your natural rhythm
Wind-Down
Wind-down preference
How much wind-down time you need
What a good wind-down looks like for you specifically
What disrupts your wind-down or makes sleep harder
Sleep Disruption & Debt
How I behave or feel when I'm sleep-deprived (my tells)
What I need to recover from sleep debt
Person B — Sleep Map
Person B
Sensory Environment
Light while sleeping
Sound while sleeping
Temperature preference
Touch / proximity while sleeping
Bedding / texture needs
Other sensory needs not listed
Chronotype
Natural sleep time (when you actually get tired)
Natural wake time (without an alarm)
How hard is waking up for you
When your cognitive energy peaks
Anything else about your natural rhythm
Wind-Down
Wind-down preference
How much wind-down time you need
What a good wind-down looks like for you specifically
What disrupts your wind-down or makes sleep harder
Sleep Disruption & Debt
How I behave or feel when I'm sleep-deprived (my tells)
What I need to recover from sleep debt
Related tools
Negotiation4.7 Overload Signals4.8 Context Load
Compare maps. Do not problem-solve yet. The goal of this step is to understand what each person actually needs, identify where those needs overlap, conflict, or run parallel, and agree on what is non-negotiable before designing anything.
Done looks likeYou have identified what is non-negotiable for each person. You have a clear picture of overlaps, conflicts, and parallel needs. You have agreed on the wind-down mode (individual, shared, or hybrid). You are ready to design.
Sensory Environment
Light
Person A
Person B
Sound
Person A
Person B
Temperature
Person A
Person B
Touch / proximity
Person A
Person B
Where our sensory needs overlap or are compatible
Where our sensory needs conflict
What is non-negotiable for each person
What we can agree to for the shared sleep environment
Chronotype
Natural sleep time
Person A
Person B
Natural wake time
Person A
Person B
Cognitive peak
Person A
Person B
How large is the chronotype gap and how does it affect the relationship currently
What we can agree to around different schedules
Wind-Down Mode
This is the most important decision in this step. The design depends on what you agree here.
Wind-down preference
Person A
Person B
Time needed
Person A
Person B
Person A — wind-down activities that work
Person B — wind-down activities that work
Where wind-down needs conflict
Wind-down mode agreementWhat our wind-down agreement looks like specifically
Sleep Disruption
Person A — top disruption factors
Person B — top disruption factors
Where disruption needs conflict
What we can agree to reduce disruption for both
Non-Negotiables
Person A — what I cannot compromise on for sleep
Person B — what I cannot compromise on for sleep
Anything the negotiation surfaced that surprised either person
Related tools
MappingDesign
Build from the negotiation output. Do not design a system based on what seems reasonable in the abstract. Design from what the maps and negotiation actually produced. If the negotiation produced an individual wind-down, design individual protocols. If it produced shared, design shared. Both are complete answers.
Done looks likeYou have a written sleep environment agreement, a wind-down protocol (individual or shared, as indicated), a morning ramp-up plan, and a low-capacity protocol. All four sections are complete enough to actually use.
Shared Sleep Environment
Light arrangement
Sound arrangement
Temperature arrangement
Touch / proximity arrangement
Other environment agreements
Wind-Down Protocol
Build this to match the wind-down mode you agreed on in Negotiation. Both individual sections are here — complete the relevant one(s).
Individual Wind-Down — Person A
When Person A starts winding down
What Person A does during wind-down
What Person A needs from the environment during their wind-down
How Person A signals they are starting wind-down
Individual Wind-Down — Person B
When Person B starts winding down
What Person B does during wind-down
What Person B needs from the environment during their wind-down
How Person B signals they are starting wind-down
Shared Wind-Down (if applicable)
When shared wind-down begins
What we do together during wind-down
How we transition to sleep (if one person goes to sleep first, if there's a signal, etc.)
Morning Ramp-Up
Different wake times and different ramp-up speeds are not problems to solve. They are conditions to design around.
Target wake time
Person A
Person B
What Person A needs in the first 30 minutes after waking
What Person B needs in the first 30 minutes after waking
Morning agreement — what we won't ask of each other before both people are fully online
How each person signals they are ready for contact or conversation
Low-Capacity Sleep Protocol
When one or both people are already sleep-deprived, demands go down and defaults go up. This protocol activates automatically.
What triggers the low-capacity protocol
Environment adjustments when sleep-deprived
What we do not ask of each other when sleep-deprived
What defaults activate (meals, tasks, conversation rules)
How we prioritize recovery
Two-Week Trial
Trial start date
What we're specifically trying for two weeks
Review date — when we return to Renegotiate
Related tools
NegotiationRenegotiate1.3 Capacity Snapshot4.3 Load Limit
Return here when something stops working. Not a full redo. Sleep systems drift because lives change, capacity changes, relationships change, and seasons change. The goal is one targeted adjustment at a time, tested for two weeks before further changes.
The date this tab was last used is visible in History. If you haven't been here in more than three months and things feel rough, that's the signal.
What's Working
What elements of the current sleep system are working well
What Stopped Working
What changed or stopped working and when
One Adjustment
Resist changing everything at once. Identify the single adjustment most likely to improve what stopped working, trial it for two weeks.
The one adjustment we're making
Trial start date
Review date
Anything else worth noting before we start the trial
Related tools
DesignMapping4.5 Capacity ResetWeekly Planner
Use when tasks are assumed but not explicitly owned, one person ends up tracking and reminding, or “I thought you had that” keeps occurring. One task, one owner, clear done state. The owner decides how. Reminders are not shared responsibility.
Done looks likeThe task moves forward without tracking, checking, or reminders.
Workspace
Task ownership lock
Task name
Owner
Definition of done (observable)
Shared location
Use when touch feels unpredictable, one partner feels pressured and the other feels rejected, or signals around closeness keep getting misread. Mark current preferences only — not ideals. Use this as a coordination reference, not a rulebook. Update it when it stops reflecting reality.
Done looks likeTouch is clearer and less loaded.
Workspace
| Person A | Person B | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Yes | No | Sometimes | Ask First | Yes | No | Sometimes | Ask First | ||
| Holding hands | |||||||||
| Hugging | |||||||||
| Sitting close | |||||||||
| Casual touch (passing by) | |||||||||
| Extended physical closeness | |||||||||
| Verbal affection | |||||||||
Use when dates feel stressful instead of connecting, or sensory overload derails time together. Define the container before choosing the activity. Plan just enough to reduce friction — not spontaneity. Agree on an exit option in advance.
Done looks likeTime together feels manageable.
Workspace
Location type
Noise tolerance
Energy level
Activity
If one of us needs to stopAgree on the exit plan before you go.
Use when both partners feel under-recognized, care is happening but not registering, or “I do a lot” keeps surfacing. Identify specific actions that feel like care when received. Keep it about actions, not explanations. Focus on the mark, not the miss.
Done looks likeAppreciation feels more accurate.
Person A — Workspace
Person A
When you do this, it feels like care to me
These actions don’t register as care
One adjustment I’ll make
Person B — Workspace
Person B
When you do this, it feels like care to me
These actions don’t register as care
One adjustment I’ll make
Use when a task was missed or abandoned and consequences worry one or both partners. Start with the miss, not the person. Keep the focus on fixing, not faulting. The repair action is a gesture, not a guarantee.
Done looks likeNext actionable step is clear.
Workspace
Execution repair
Task missed
What happened (one sentence)
Repair action
Reminder: The repair action is a gesture, not a guarantee.
Use when you need to initiate a conversation about redistributing household labor but don’t know how to open it without it becoming a conflict. Each script leads with system problems, not personal blame. Adapt the language to fit your relationship — use the notes field under each one.
1
Pick the script that matches your current situation. Read it through once before using it.
2
Adapt the bracketed sections and any phrasing that doesn’t fit your relationship.
3
Use it at a low-capacity-neutral time — not mid-conflict.
Done looks likeA conversation has been opened and a next step (trial, review date, or domain assignment) is agreed on.
Scripts
1
Opening the Conversation
▼
“I need to talk about how we’re handling household stuff. I’ve been tracking my capacity, and I’m realizing that the way we’re dividing things isn’t sustainable for me. I’m not blaming anyone — I’m just noticing I’m hitting overload regularly, and I think we need to redesign how things work. Can we set aside time to look at this together?”
Notes & adjustments
2
Explaining Invisible Labor
▼
“I want to share something I’ve been learning about. There’s a difference between doing tasks and managing tasks — like, I might ask you to pick up groceries, but I’m the one remembering we need them, checking the list, figuring out what we’re making for dinner, and planning the week. That mental work is invisible labor, and it’s draining my capacity. Can we talk about redistributing some of that planning and remembering work?”
Notes & adjustments
3
Proposing Domain-Based Division
▼
“I have an idea for how we could divide household work differently. Instead of splitting every task, what if we each owned whole domains? Like, you handle ALL the kitchen stuff — groceries, cooking, dishes, planning meals. I handle ALL the laundry — sorting, washing, folding, putting away. That way we’re not coordinating constantly, and each person can develop their own system. Would you be open to trying that?”
Notes & adjustments
4
Creating Hard-Day Protocols
▼
“I need us to have a plan for when one of us is at low capacity. Right now, when I’m overwhelmed, things just fall apart or you end up doing everything. Can we create a ‘hard day’ version of our household system? Like, what are the absolute minimums that have to happen, and how do we shift responsibilities when someone can’t do their usual stuff?”
Notes & adjustments
5
Addressing Mismatched Standards
▼
“I think we have different standards for [cleanliness / organization / timing], and that’s creating friction. I’m not saying one of us is right or wrong, but I need us to agree on what ‘done’ looks like for different tasks. Can we go through our main household tasks and define what completion actually means, so we’re not redoing each other’s work or feeling like the other person isn’t doing enough?”
Notes & adjustments
6
When Systems Break Down
▼
“The system we set up isn’t working the way we planned. I’m not blaming you — systems fail for lots of reasons. But I think we need to troubleshoot it. Can we look at where it’s breaking down? Maybe the setup was too complicated, or we didn’t account for something, or our capacity has changed. Let’s figure out what needs to change.”
Notes & adjustments
Key Principles
Lead with system problems, not personal blame. “The system isn’t working” not “You’re not doing enough.”
Use capacity language to depathologize struggles.
Propose experiments, not permanent changes. “Let’s try this for 2 weeks and see.”
Acknowledge when your expectations were misaligned with reality.
Name when something works only because someone is pushing through.
Return to shared goals. “We both want a household that doesn’t drain us.”
Related tools
5.1 Task Ownership Lock
5.5 Execution Repair
1.4 Working Agreements
Guide: Invisible Labor
Guide: Capacity
Use when invisible labor is uneven but unseen. Each person checks everything they currently handle — visible and invisible. Then compare perception gaps at the end. The goal is visibility, not victory.
Done looks likeBoth people have named at least one item they assumed only they were carrying. At least one gap has a next step.
Person A
Labor That’s Visible
Household / Life Admin
Relational Maintenance
Logistics
Labor That’s Invisible
Labor That's Invisible
Relational Maintenance
Logistics
Person B
Labor That’s Visible
Household / Life Admin
Relational Maintenance
Logistics
Labor That’s Invisible
Labor That's Invisible
Relational Maintenance
Logistics
Discuss “Invisible Credits”
What did you select that you assumed only you dealt with?
What did you check unaware your partner also finds exhausting?
Which load gaps need support, relief, or a language change?
We work as a team to bridge perception gaps — not shape-shift beliefs.
Related tools
5.6 Renegotiation Scripts
5.1 Task Ownership Lock
Guide: Invisible Labor
Maps the invisible work your brain and body do that doesn't show up on a to-do list. Invisible load uses real capacity — cognitive, emotional, social, and physical — but because it's invisible, it's often unrecognized, unshared, and unaccounted for. Each person completes their own section independently. Compare after.
Done looks likeBoth people have checked what they carry. At least one load gap has been named. At least one redistribution or language change is identified.
Person A — What I Currently Carry
Person A — what surprised you most in your own list
Person B — What I Currently Carry
Person B — what surprised you most in your own list
Compare & Redistribute
What did you each check that you assumed only you were carrying?
Where is load overlapping — both people carrying similar hidden weight?
Which gaps need redistribution, outside support, or just language change?
One concrete load shift to try this week
Related tools
5.7 Labor Inventory5.6 Renegotiation ScriptsGuide: Invisible LaborAssess: ILCOA
Why things break down — and why trying harder doesn’t fix it.
Understanding this cycle changes what interventions are worth making.
Mismatch → Overload → Distress
Mismatch
→
Overload
→
Distress
→
Can’t address mismatch
Mismatch
Relational strain rarely starts with conflict. It starts when environmental demands don’t align with what a nervous system can sustainably handle.
One partner needs silence to process emotion; the other needs verbal connection to feel close. One regulates through movement and intensity; the other through stillness and predictability. Neither approach is wrong. When the differences stay unnamed and unaccommodated, they create persistent friction — not because anyone is failing, but because the system isn’t designed for both nervous systems at once.
Overload
Unaddressed mismatch accumulates. Overload happens when demands exceed available capacity long enough that recovery can’t keep pace with depletion.
The nervous system starts drawing from reserves. Sleep quality drops. Irritability increases. Flexibility narrows. Small things that were once manageable feel overwhelming.
Overload looks different across neurotypes. An autistic partner may become quieter, sharper, or withdraw entirely. An ADHD partner may become more reactive, forget commitments, or struggle to complete tasks. A neurotypical partner may feel disconnected, unappreciated, or constantly on guard.
Distress
Distress is the point at which the nervous system can no longer maintain baseline functioning. Communication skills go offline. Emotional regulation becomes harder. The ability to perspective-take or hold nuance disappears. Both partners may become versions of themselves they don’t recognize.
And distress makes it nearly impossible to address the original mismatch. The cycle feeds itself.
The key insight: Most relationship advice assumes the cycle is not running. It targets communication skills that require regulation to work. When the cycle is active, better communication tools alone cannot interrupt it — because the problem is structural, not personal.
Why Standard Advice Fails Here
“Talk it through” assumes both nervous systems can access language and flexibility during conflict. For many neurodivergent adults, this isn’t true when regulation is already compromised. Pushing for resolution before regulation is restored makes things worse.
“Compromise” assumes that splitting the difference creates workable middle ground. Splitting neurological needs doesn’t produce two people who are adequately served. It produces two people who are both depleted.
“Try harder” assumes capacity is fixed and effort is the variable. Capacity fluctuates constantly. Effort without structural change accelerates burnout.
People are not broken. Systems are mismatched. That difference determines what kind of work will actually help.
Tools that address this directly
1.3 Capacity Snapshot
3.1 Early Warning Signs
3.2 Time-Out Plan
4.1 Escalation Catch
4.5 Capacity Reset
What I took from this — The Cycle
What does this cycle look like in your relationship specifically?
Capacity is not character. It is not something you have more or less of because you are disciplined or resilient. Understanding what capacity actually is changes how you interpret low-capacity behavior — in yourself and in your partner.
What Capacity Actually Is
Capacity is the available mental, emotional, physical, and sensory resources a person has at any given moment.
It is dynamic. It fluctuates day to day, sometimes hour to hour, based on variables that are often invisible to others: sleep quality, sensory environment, emotional demand, cognitive load, pain, hormones, recent stress exposure, and recovery time since the last period of overload.
What Shapes Capacity
Sleep quality is one of the strongest predictors of same-day capacity. Even one night of poor sleep measurably reduces emotional regulation, flexibility, and executive function.
Sensory environment draws from the same capacity pool as emotional and cognitive processing. High sensory load reduces what’s available for everything else — including relationship work.
Cognitive load accumulates invisibly. Planning, remembering, tracking, and coordinating use real resources, even when none of those tasks feel “hard.”
Recovery time after an overload period is not optional — it is the mechanism that restores capacity. Without it, baseline drops progressively.
Neurodivergent Capacity Differences
Why Capacity Looks Different Across Neurotypes
Neurodivergent adults often experience capacity differently than neurotypical adults. Sensory overload, attentional saturation, social demand, and executive load may deplete capacity faster and require longer recovery.
ADHD intensity and autistic regulation needs can create patterns where high motivation coexists with low tolerance. What looks like inconsistency is often fluctuating capacity — not unreliability.
In mixed-neurotype relationships, one partner may have reliable capacity for social plans, verbal processing, and multitasking. The other may have capacity for focused work and quiet routines, but very little for spontaneity or open-ended conversation. Neither nervous system is wrong. They are simply different.
When relationships are designed as if capacity is uniform and stable, they break down in predictable ways. Designing for actual capacity — not ideal capacity — is the structural fix.
Tools that address this directly
1.3 Capacity Snapshot
4.3 Conversation Load Limit
4.4 External Stress Containment
4.5 Capacity Reset
1.4 Working Agreements
What I took from this — Capacity
What did you learn about your own capacity that you hadn't named before?
One of the most consistent sources of strain in mixed-neurotype relationships is labor that never gets named — because it’s invisible to both people carrying it and not carrying it.
Cognitive Labor
The Work Behind the Work
Cognitive labor is the work of planning, remembering, anticipating, coordinating, and managing systems. It is not the same as executing tasks. It is the invisible architecture that allows tasks to happen.
In many mixed-neurotype relationships, one partner holds the household schedule, anticipates what needs to happen next, remembers appointments and commitments, manages transitions, and coordinates shared life. The other partner executes tasks when asked but is not carrying the mental load of planning and anticipation.
Both partners feel they are contributing. The person carrying cognitive labor feels exhausted and unsupported. The person executing tasks feels unappreciated and confused about what more they could possibly do. Both are correct from within their own frameworks. Neither can see the full system.
This is not a problem of intention. It is a problem of invisible work. When labor is invisible, it cannot be redistributed. The person carrying it burns out. The other person remains unaware. Resentment builds.
Emotional Labor
Managing the Relational Climate
Emotional labor functions similarly. One partner may be managing tone, smoothing conflict, initiating repair, monitoring the emotional climate of the relationship, and absorbing the other’s dysregulation.
This work is real, constant, and depleting. It is also frequently unrecognized because it is expected as part of care — particularly from partners socialized to be emotional caretakers.
When emotional labor is invisible, it creates the same pattern as cognitive labor: the person carrying it accumulates strain without language to describe it. The person not carrying it cannot address what they cannot see.
Making It Visible
Instead of “Why don’t you do more?” — where is cognitive load concentrating, and how could it be redistributed?
Instead of “Why don’t you care?” — what does care look like in this nervous system, and is it being recognized as care?
Instead of “Why are you always exhausted?” — what invisible work is being absorbed, and is that distribution sustainable?
Making invisible labor visible doesn’t automatically solve it. But it shifts the conversation from “What is wrong with us?” to “What is this system actually doing?”
Tools that address this directly
5.1 Task Ownership Lock
5.4 Appreciation That Lands
5.5 Execution Repair
1.4 Working Agreements
1.3 Capacity Snapshot
What I took from this — Invisible Labor
Where is invisible labor concentrating in your relationship?
Sustainable mixed-neurotype relationships require two kinds of work happening simultaneously. Not sequentially. Not one before the other. Both at once. Understanding why both pathways matter — and what breaks when only one moves — changes what to work on first.
Systems Alignment
Modifying environmental conditions to improve fit. Schedule restructuring. Sensory environment modification. Communication protocol development. Task redistribution. Clearer recovery time.
Narrative Repair
Examining the meanings people have constructed about their experiences — where those meanings came from, why they persist, whether they still serve.
Why Systems Alignment Alone Isn’t Enough
Many couples implement schedules, create task lists, and negotiate responsibilities. On paper, everything looks better. In practice, resentment builds, compliance is fragile, and changes don’t hold.
If an autistic partner agrees to initiate more physical contact but the meaning attached to touch is “This is uncomfortable and I am doing it to avoid conflict,” that accommodation won’t feel like care. It will feel like performance. Over time it becomes unsustainable.
Structure without meaning produces compliance, not connection.
Why Meaning Work Alone Isn’t Enough
Other relationships process emotions, explore patterns, work on self-compassion. Insight deepens. Understanding grows. Yet daily life doesn’t improve.
If a partner works hard to believe they deserve accommodation but their actual environment still punishes asking for it, the new meaning has no foundation to stand on. If a partner commits to reframing their partner’s forgetting as neurological rather than personal, but they are still carrying 90% of household cognitive labor, exhaustion will override the reframe.
Meaning without structure produces understanding, not change.
How the Pathways Interact
Systems alignment creates the conditions for new meanings to form. When structure changes, new experiences become possible. New experiences produce evidence that the old meaning was context-specific, not universal.
Narrative repair creates the emotional capacity to engage with systems changes. If the meaning attached to asking for help is “I will be hurt,” no amount of structural invitation will feel safe until that meaning shifts.
The process is recursive, not linear. Each pathway shift enables the other. Small structural adjustments create new evidence. New evidence enables small meaning shifts. Small meaning shifts make further structural adjustments feel possible.
Both pathways must move. The question is not whether to do this work. It is whether to do it with the right tools or continue struggling without them.
What This Looks Like in Practice
Dual Pathway Work in Every Tool
When a couple establishes a protocol for managing conflict, they are not just agreeing on time-outs and repair scripts. They are also processing what shutdown means, what pursuit signals, and whether emotional intensity is interpreted as danger or passion.
When partners redesign their social life so one can have independent friendships while the other stays home, they are not just solving a logistics problem. They are also reworking the meanings attached to togetherness, autonomy, and what it means to be a good partner.
The systems work creates safety. The meaning work creates access to that safety.
All tools work on both pathways — start anywhere that matches the current friction point
1.1 Mini-Glossary
1.2 Signal Map
3.5 Repair Scripts
4.2 Regulation Plan
5.4 Appreciation
What I took from this — Dual Path
Which pathway needs more attention right now — systems or meaning?
Reference — Use when one person is being misunderstood as angry, cold, uncaring, or lazy. Each of these states has different internal experience, external signs, and common misinterpretations. Describe your own version in the tools below.
Internal State Decoder
Shutdown
Internal
Brain feels foggy. Speech is delayed or absent. Energy is critically low.
ExternalUnresponsive or unable to speak. Eyes down or closed.
Misread asSilent treatment. Zoned out.
Overwhelm
Internal
Too much input, feeling, or demand. Brain feels hijacked. Urgency and confusion.
ExternalAgitation or distress. Rapid speech. Attempts to flee or leave.
Misread asStonewalling. Zoned out. Overreacting.
Distraction
Internal
Brain feels scattered. Hard to filter signal from noise.
ExternalInattention. Physical restlessness. Partial eye contact.
Misread asDramatic / irrational. Using excuses.
Disengagement
Internal
Brain feels numb or disconnected.
ExternalChecked out. Appears not to be listening.
Misread asApathy / coldness. Avoids intimacy. Doesn’t care.
My Personal Version
Write the specific version of each state that applies to you. This is what your partner actually needs to recognize — not the generic version above.
SHUTDOWN
Person A — what this looks like for me specifically
Person B — what this looks like for me specifically
OVERWHELM
Person A — what this looks like for me specifically
Person B — what this looks like for me specifically
DISTRACTION
Person A — what this looks like for me specifically
Person B — what this looks like for me specifically
DISENGAGEMENT
Person A — what this looks like for me specifically
Person B — what this looks like for me specifically
Related tools
1.2 Signal Map
2.6 Translation
3.1 Early Warning
4.1 Escalation Catch
What I took from this — State Decoder
Which state is most often misread in your relationship, and how?
◆ Optional Assessment Suite
The Household Operating System Builder is a nine-instrument assessment suite. It maps how a household actually functions under real conditions — not how it should work, and not who is at fault.
Each instrument measures a different layer of strain. Together, they allow those answers to be connected. This is what makes the suite a suite rather than a collection — results from one assessment inform how results from another should be understood.
Each instrument measures a different layer of strain. Together, they allow those answers to be connected. This is what makes the suite a suite rather than a collection — results from one assessment inform how results from another should be understood.
Where to Begin
There is no correct order. The tools work together but are not meant to be completed all at once. This page exists to reduce decision load.
You do not need to start where the problem feels loudest. Beginning with one tool is enough. If choosing feels hard, that is often a sign to begin with capacity, not conflict.
The Nine Instruments
How They Connect
How the nine instruments read together as a suite
Using Over Time
How to return to the suite as conditions change
Capacity Reality Mapping (CRM) — Measures how much demand your household can reliably handle. Rate what works without pushing, masking, or paying a cost later.
Section A — System Capacity Ratings
Section B — Timing & Mismatch
Check any that are often true
When one person is overwhelmed, what usually happens?
Section C — Hard-Day Impact
On low-capacity days, what does NOT work well?
Section D — System Limits
For the system to stay sustainable, it should NOT require:
Scores
SCF
—
System Capacity Floor
0–4: lowest A score
CSS
—
Capacity Spread Score
0–4: max–min of A scores
AI
—
Asynchrony Index
0–6: B1–B6 checked
LCIS
—
Low-Capacity Impact
0–7: C items checked
BLS
—
Boundary Load Score
0–6: D items checked
Profile A
Overloaded System
SCF ≤ 1 AND LCIS ≥ 4. Reduce demands. Stabilize before redesign.
SCF ≤ 1 AND LCIS ≥ 4. Reduce demands. Stabilize before redesign.
Profile B
Fragile System
SCF = 2 AND (CSS ≥ 2 OR AI ≥ 3). Fix lowest area first.
SCF = 2 AND (CSS ≥ 2 OR AI ≥ 3). Fix lowest area first.
Profile C
Misaligned System
SCF ≥ 2 AND AI ≥ 4. Design for mismatch. Reduce coordination demands.
SCF ≥ 2 AND AI ≥ 4. Design for mismatch. Reduce coordination demands.
Profile D
Stressed but Adaptable
SCF ≥ 3 AND LCIS ≤ 2 AND BLS ≤ 2. Refine for clarity.
SCF ≥ 3 AND LCIS ≤ 2 AND BLS ≤ 2. Refine for clarity.
What this told us (CRM)
What did your capacity scores tell you about the system right now?
Invisible Load & Cognitive Ownership (ILCOA) — Identifies where invisible work lives: thinking, remembering, tracking, deciding, monitoring. If something only works because someone compensates, count it as high load.
Section A — How Much Invisible Load Exists
Section B — Where Invisible Load Lives
B1. How many people carry most of the invisible load?
B2. How visible is invisible load?
B3. How stable is invisible load?
B4. How negotiable is invisible load?
Section C — How the System Fails
C1. When invisible load drops, what fails first? (check any)
C2. What must happen for tasks to move forward?
C3. What does failure cost?
C4. How often do these failures occur?
C5. How predictable are these failures?
Section D — What Stress Does to the System
D1. During stress or low-capacity periods, the system tends to:
D2. Stress usually causes:
Scores
TILS
—
Total Invisible Load
0–24 | Low 0–6 | Mod 7–12 | High 13–18 | Extreme 19+
LCS
—
Load Concentration
0–12 | Distributed 0–3 | Uneven 4–7 | Unsafe 8+
SFIS
—
System Failure Impact
0–26 | Resilient 0–6 | Fragile 7–13 | Prone 14+
SDS
—
Stress Destabilization
0–18 | Absorbed 0–4 | Strains 5–10 | Destabilizes 11+
If a system only works because someone is compensating, the system is not working.
What this told us (ILCOA)
Where is invisible load concentrating, and what does that explain?
Task Friction & Failure Mode Assessment (TFFMA) — Identifies where tasks fail, stall, or repeatedly collapse. If something works only because someone pushes or compensates, count it as friction.
Section A — How Much Friction Exists
Section B — Where Task Friction Comes From
Section C — How Tasks Fail
C8. How often do failures disrupt the system?
C9. How predictable are failures?
Section D — Conditions That Affect Failure
Risk factors
Protective factors (higher = better)
Scores
TTFS
—
Total Task Friction
0–32 | Low 0–8 | Mod 9–16 | High 17–24 | Severe 25+
FSS
—
Friction Source Score
0–27 | Few 0–6 | Some 7–13 | High 14+
FPS
—
Failure Pattern Score
0–27 | Low 0–6 | Mod 7–13 | High 14+
SSI
—
Stress Sensitivity
0–15 | Protected 0–3 | Sensitive 4–7 | Reactive 8+
TSII
—
Task System Impact
0–101 | Stable 0–25 | Fragile 26–50 | Prone 51+
If tasks only work through urgency, reminders, or one person compensating, the system is not designed to succeed.
What this told us (TFFMA)
What tasks are structurally set up to fail, and why?
Communication-to-Action Translation Map (CATM) — Measures how well communication converts into shared meaning, plans, and follow-through. If action happens only because someone tracks, reminds, or compensates, score higher.
Section A — Clarity & Shared Meaning
Section B — Decision-to-Plan Conversion
Section C — Follow-Through & Execution Breakdowns
Section D — Translation Supports (higher = better)
Scores
CFS
—
Clarity Friction
A1–A10 sum (0–40)
PCFS
—
Plan Conversion Friction
B1–B10 sum (0–40)
EBS
—
Execution Breakdowns
C1–C10 sum (0–40)
TSSS
—
Support Strength
D1–D10 sum (higher = better)
STSI
—
System Translation Strain
(A+B+C)−D | Protected 0–10 | Sensitive 11–30 | Unstable 61+
If communication only turns into action through reminders or compensation, the system — not the people — needs redesign.
What this told us (CATM)
Where does understanding stop turning into action?
Sensory–Environment Fit Matrix (SEFM) — Maps sensory and environmental factors that increase load, reduce regulation, or interfere with functioning. Answer based on typical impact, not best days.
Section A — Strain-Triggering Conditions
Section B — Contexts That Need Protection
Check contexts that apply, then rate the overall system cost (0–4)
Pattern check
Section C — What Breaks First
When environmental strain is high, what tends to fail?
Section D — Recovery Cost
Section E — Existing Buffers (higher = more protected)
Scores
A
—
Trigger Load
A1–A12 sum
D
—
Recovery Cost
D1–D6 sum
E
—
Buffers
E1–E6 sum (higher = protected)
ETI
—
Environmental Trigger Index
(A+B+C+D)−E, min 0
Environmental strain is predictable. Planning for it is how systems stay functional.
What this told us (SEFM)
What environmental conditions are driving more strain than you realized?
Transition & Predictability Needs Profile (TPNP) — Measures how your household handles transitions and predictability. If something works only because someone compensates, score higher.
Section A — Transition Load
Section B — Predictability Requirements
Section C — Change Impact
Section D — Buffers & Defaults (higher = better)
Scores
TLS
—
Transition Load
0–40 | Low 0–10 | Mod 11–20 | High 21–30 | Severe 31+
PRS
—
Predictability Requirements
0–40 | Low 0–10 | Very high 31+
CIS
—
Change Impact
0–40 | Low 0–10 | Severe 31+
BDSS
—
Buffer Strength
0–40 (higher = more protected)
SSI
—
System Sensitivity Index
(TLS+PRS+CIS)−BDSS | Protected 0–10 | Unstable 61+
If transitions only succeed because someone compensates, the system — not the people — needs redesign.
What this told us (TPNP)
Where are transition costs higher than the system accounts for?
Collapse, Burnout & Recovery System Map (CBR-SM) — Looks at how the system moves through periods of strain, collapse, and recovery. Rate the last 30–60 days.
Section A — Strain Detection
Section B — Collapse Patterns
Section C — Recovery Cost
Section D — Protections & Buffers (higher = better)
Scores
A
—
Strain Detection
A1–A12 sum (0–48)
B
—
Collapse Patterns
B1–B12 sum (0–48)
C
—
Recovery Cost
C1–C12 sum (0–48)
D
—
Protections
D1–D12 sum (0–48, higher = better)
Core
—
Burnout Cycle Score
(A+B+C)−D | Buffered 0–20 | Sensitive 21–50 | High-strain 51–90 | Collapse-driven 91+
A high score can reflect insufficient external support — not poor effort or a bad partnership.
What this told us (CBR-SM)
What does the collapse pattern look like, and what would interrupt it earlier?
Repair & Rupture Operating Map (RROM) — Identifies where strain concentrates during rupture and repair. Answer based on what usually happens, not best moments.
Section A — Noticing Rupture Early
Section B — Common Sources of Rupture Strain
Check any that occur, then rate how much strain they add
Section C — What the System Does Under Strain
Section D — Responses That Affect Strain
Responses that reduce strain (how well they work for you)
Responses that add strain (how often these occur)
Section E — Repair Timing
Section F — Repair Communication
Section G — Repair Actions
Actions that reduce strain
Actions that add strain
Section H — When More Support Is Needed
Scores
ESI
—
Early Signal Index
A1–A9 average (0–4)
EscI
—
Escalation Index
C1–C9 average (0–4)
StabI
—
Stabilization Index
D1–D6 average (0–4)
RSI
—
Repair Structure Index
(E+F+G) avg ÷ 3
ERF
—
Extended Repair Flag
H avg ≥ 2.5 = Yes
Repair becomes safer when the system has enough structure to support it. High H scores mean slower repair is appropriate, not impossible.
What this told us (RROM)
What is repair actually resolving, and what is it leaving in place?
Value Strain Patterns (VSP) — Detects where values create friction because of ambiguity, competing priorities, or exceeding available capacity. Does not judge values or assign blame.
Section A — Clarity Strain
Section B — Priority Mismatch Strain
Section C — Translation Strain
Section D — Maintenance Strain
Section E — Protective Supports (higher = more protected)
Scores
Clarity
—
Clarity Strain
A1–A5 (0–20)
Priority
—
Priority Mismatch
B1–B5 (0–20)
Translation
—
Translation Strain
C1–C5 (0–20)
Maintenance
—
Maintenance Strain
D1–D5 (0–20)
Protection
—
Protection Score
E1–E5 (0–20, higher = better)
Pattern 1
Undefined Values
Highest: Clarity Strain. Define one value in plain language first.
Highest: Clarity Strain. Define one value in plain language first.
Pattern 2
Priority Mismatch
Highest: Priority Strain. Name competing values and agree which leads when.
Highest: Priority Strain. Name competing values and agree which leads when.
Pattern 3
Translation Gap
Highest: Translation Strain. Turn one value into one clear rule.
Highest: Translation Strain. Turn one value into one clear rule.
Pattern 4
High Maintenance
Highest: Maintenance Strain. Change the system so values hold without enforcement.
Highest: Maintenance Strain. Change the system so values hold without enforcement.
Pattern 5
Supported but Fragile
Moderate A–D, low Protection. Strengthen one protective support first.
Moderate A–D, low Protection. Strengthen one protective support first.
If a value only works because someone tolerates exhaustion or repeated repair, the issue is strain — not commitment.
What this told us (VSP)
Which value is creating the most strain, and what would reduce it without abandoning it?
System Snapshot — A quick picture of how the household system is functioning right now. This reflects current conditions only. Not a plan or a promise.
Overall System Capacity Right Now
Active Sources of Strain
What is working better than it used to
What feels unsustainable if nothing changes
What this system needs more of right now
This snapshot is information, not a plan or a promise.
Revisit Prompt
For returning to the tools without starting over. You do not need to redo everything. Start with the tool that matches the current strain. Different results do not mean anyone was wrong before.
What feels lighter, heavier, or different since last time?
Has any new pressure entered the system?
If the urge is to fix everything immediately, that usually means capacity is lower than the problem deserves. Begin with understanding, not action. Insight does not obligate immediate change. Coming back with clearer understanding is already movement.
What Changed Because We Looked
Not about outcomes, fixes, or improvement. About what shifted simply because the system was made visible. Use after completing one or more assessments, or when reflecting back on earlier work.
What makes more sense now than it did before?
What stopped feeling personal or moral?
What is no longer being asked of the system?
What expectations softened, narrowed, or became more realistic?
What feels easier to name, even if it is not resolved?
Not all meaningful change looks like action. Sometimes the most important shift is knowing what is actually happening.
The nine instruments are designed so results from one inform how results from another should be understood. Patterns that look confusing or contradictory when viewed alone often make sense once placed in context with the rest of the tools.
The value of the suite is not in coverage or completion, but in coherence. Each instrument helps narrow the question from “what is wrong” to “where is pressure coming from, and why does it keep landing here.”
Each Instrument’s Role in the Suite
Reading the Suite as a Whole
Capacity and load shape execution. Execution under pressure reveals environmental and predictability mismatches. Repeated strain over time clarifies burnout and recovery patterns. Repair shows whether change holds. Values strain reflects where meaning and capacity are no longer aligned.
Task failure often reflects capacity limits or invisible load. Communication strain often reflects transition pressure or environmental overload. Burnout often reflects unresolved strain that has been cycling across the system rather than a single issue.
Reading the suite as a whole reduces false conclusions. Instead of asking who should try harder, it supports identifying where conditions need to change so the household can function more sustainably.
This suite is not designed to be completed once and set aside. It is designed to be returned to as conditions change. Household systems are not static. Results that look different over time are not contradictions. They are information about changing conditions.
Using This Over Time
You may notice that some tools feel relevant at certain moments and not at others. That is expected. You do not need to use every assessment every time. Returning to one tool can be enough to re-orient the system.
It is also normal for insight to arrive before change is possible. Understanding what is happening does not obligate immediate action. In many cases, clarity itself reduces strain by removing self-blame or unrealistic expectations.
When to Pause
If using these tools increases distress, conflict, or pressure, that matters more than completing the assessment. Pausing is appropriate when:
Emotions escalate faster than understanding
Results are being used to argue, persuade, or prove a point
Someone feels pressured to continue or disclose
Safety, consent, or regulation feels compromised
These tools assume a baseline level of safety. They are not meant to be used to resolve coercion, control, or active harm. In those situations, outside support is more important than further system mapping. Stopping, slowing down, or setting the tools aside is a valid and responsible choice.
Closing
The Household Operating System Builder was created to support understanding, not compliance. It begins from the assumption that people are already doing the best they can within the limits of their capacity, environment, history, and available support.
When systems struggle or break down, it is rarely because individuals failed to care, communicate, or try hard enough. More often, it is because the structure of the household was asked to carry more than it could realistically sustain.
You are not required to agree with every framework, complete every assessment, or arrive at solutions. You are not required to act on insight immediately, or at all. Understanding does not obligate change.
You are allowed to take what is useful and leave the rest.
Your data saves to your account automatically. Use Print / Save PDF to share a session summary with a therapist.