Build a relationship toolkit of agreed codes
Don't assume a traditional relationship template fits — co-create an explicit 'toolkit' of communication codes with your partner, including a sign-language or signed system for when one of you goes non-verbal under overload. Keep the norms that serve you, discard the ones that don't, and add tools (like a guaranteed decompression window after a hard day) that a standard template never provides.
This page isn't typically flagged for the selected profile — shown because you opened it directly.
Autistic partners can lose speech during overload, and traditional relationship norms have no provision for that — so building the relationship on an unexamined default template leaves you without the tools you actually need. The better approach is to co-create a shared toolkit explicitly with your partner: a set of agreed communication codes for the situations that come up, including a pre-agreed signed or sign-language system to keep communicating (and keep consent live) when words aren’t available. Two design rules make this work. First, treat the standard relationship template as optional — keep the norms that genuinely serve you both and discard the ones that don’t, rather than importing them wholesale. Second, add the tools a default template omits — for example an agreed, honoured window of silent decompression (half an hour to an hour of no talking) after coming home overloaded with information, so recovery doesn’t force masking or tip into a meltdown at home. The result is a relationship engineered around how the two of you actually work, with explicit protocols for the hard moments instead of an assumption that words will always be available.
