For Couples In development

Two portraits. One conversation.

Most couple quizzes hand you a score and call it insight. Wrenlight is building something quieter and more useful: a discussion framework woven from everything each of you has learned about yourself here — without either of you having to hand over a single test result.

Nothing shared without both saying yes Insights, never raw results No compatibility score — ever Either of you can dissolve it anytime

The idea

You've each taken tests here — how you fight, how care lands, what recharges you, how you repair. Each result is private, and stays private. But between two portraits there's a third thing: the pattern between you. Where you're naturally aligned. Where you differ in ways that quietly do work for the relationship. And where you differ in ways that keep producing the same Tuesday-night argument.

Wrenlight for Couples reads both portraits and writes about that third thing only. Not "she's an Avoider," not "he scored 71 on closeness" — but "one of you needs space before words come, and one of you needs words before space feels safe. Here's what to do with that."

How it will work

STEP 1
Take tests separately

Each of you builds your own portrait, on your own account, in your own time. Nothing about this step is shared.

STEP 2
Both say yes

One of you sends a couple invite; the other accepts. Double opt-in, every time a framework is generated. Either of you can revoke it, and the framework dissolves.

STEP 3
Wrenlight weaves

The synthesis reads both portraits and writes only about the pattern between you — derived insights, never scores, types, or answers.

STEP 4
You talk

You get a discussion framework: dos & don'ts, accommodations each of you can make, and conversation starters. It's an agenda, not a verdict.

The privacy model

This only works if neither of you has to trade away your private results to get the shared picture. So the boundary is structural, not a setting:

What the framework contains

  • Patterns between you — alignment, complement, friction
  • Dos & don'ts, written symmetrically — both of you always get an accommodation
  • Conversation starters drawn from your actual dynamics
  • How the picture deepens as more tests are woven in

What stays yours alone

  • Your individual test results and archetype names
  • Your dimension scores — all of them
  • Which test (or answer) produced any given insight
  • Anything you took before — or after — the couple link

One more rule, and it's the most important one: every friction insight is written symmetrically. There is no version of this framework that says one of you is the problem. If a pattern needs an accommodation, both of you get one.

See what your tests would unlock

The framework is built from the tests you've both taken. Check off tests below as if you and your partner had each done them, and watch the report take shape. The example insights are from a fictional couple — Maya & Sam.

Build a sample framework

0 of 24 tests

Assume both of you take each test you check. Two tests in a theme open that chapter; more tests deepen it.

✓ marked = tests you've already taken — your half of those is already done.
Framework depth: Nothing yet
Your sample framework — Maya & Sam

A page from a finished framework

Here's the texture of the real thing — one aligned pattern, one complementary one, one friction pattern, fully written. Notice what's absent: no types, no scores, no winner.

Worked example · Maya & Sam · fictional

Where you meet, where you trade, where you grind

Built from 11 tests each. Three of nine chapters shown.

Aligned — costs them nothing

Maya and Sam both repair fast and forgive faster

Neither of them is a grudge-keeper. After a rupture, both reach for repair within hours, not days, and neither needs the other to grovel. This is rarer than it feels from the inside — protect it. The one watch-out: fast repair can paper over a pattern that needed a longer look. Once a season, the framework suggests asking: "is there anything we keep apologizing for instead of changing?"

Complementary — quietly doing work for them

Sam plans the holiday; Maya makes it a story

Sam builds the scaffolding — bookings, routes, the reservation that saved the evening. Maya supplies the appetite — the detour, the conversation with the stranger, the reason there's a story to tell at all. Each has probably read the other as "rigid" or "flaky" at some point. The framework's read: they are each other's missing half of the same competence. The accommodation is one sentence each, occasionally: thank the other for the half you don't do.

Friction — needs a protocol, not a winner

Heat meets distance

When conflict sparks, Maya moves toward it — voice rises, words come fast, and engagement feels like caring. Sam goes quiet and needs to leave the room to find his actual position. Each reads the other's move as the threat: pursuit feels like attack; retreat feels like abandonment. Neither read is true. So the protocol has two halves — one for each seat:

If Maya presses

DoLet the pause happen. Write down the one sentence that most needs to be heard — it will survive the hour.

Don'tFollow Sam into the next room, or treat the pause itself as the verdict.

If Sam pauses

DoCall the pause with a return time — "I need an hour, I'm back at 9" is a complete sentence — and keep it.

Don'tLet the silence stretch past the agreed time. From Sam's side, that's what breaks the deal.

Every insight above is derived. Maya never sees Sam's conflict-style result; Sam never learns Maya's attachment reading. The framework speaks only in patterns-between — and every friction pattern carries an accommodation for each name, never just one. In your framework, your names sit where theirs do.

The methodology, briefly

The same instruments that power your Portrait power this — scenario-based questions, three measurements per trait, honest valence handling. The couple synthesis adds three rules of its own:

Three pattern types, no score

Every cross-portrait finding is classified as aligned, complementary, or friction-prone. Nothing is ever summed into a number. Compatibility scores read as prognosis — and couples don't need a prognosis, they need a protocol.

The symmetry rule

Friction insights must name an accommodation for each partner or they don't ship. The framework is structurally incapable of taking sides.

Depth honesty

Chapters only open when enough overlapping tests support them — a minimum of two per theme, eight or more for the full framework. Thin data gets a thin claim or none, never filler.

This is in development. The single best way to be ready for it — and to make your half of the framework rich from day one — is to keep building your own portrait now.

Start building your half →
Noted — you'll see it here first. Until then, every test you take now is a head start.