There is a particular pleasure in watching something you designed unfold exactly as designed. Not control for its own sake — the satisfaction of a plan meeting reality and holding. If that sentence describes you more than it describes most people, the Compass has put you in roughly the right place.
LMIR is Lead, Mind, Intense, Ritual. You steer. It happens in your head more than in your hands. You like it to run hot. And you want the shape agreed before anyone touches anyone.
What this actually looks like
Rarely dramatic. On an ordinary Tuesday it looks like deciding at four in the afternoon what will happen at ten, and saying so — not as a request but as information. It looks like an order of events: this, then this, and the third thing only if the first two went well.
It looks like rules that are small enough to keep. Not “you will obey me”, which is unenforceable and faintly silly on a weeknight, but “you do not touch yourself until I say” — specific, checkable, and finite.
And it looks like a scene that ends when you said it would end, because the ending was part of the design.
Architects also negotiate well. Not because they are unusually ethical but because precision is how they think anyway — the same instinct that wants the order of events settled also wants the limits settled, and asks about them in more detail than most people bother with.
That makes you unusually safe to play with, and it is worth knowing, because the trait can feel clinical from the inside. It is not. Being asked exactly what you do and do not want, by someone who is clearly writing it down somewhere behind their eyes, is its own kind of attention.
Most Architects under-ask in one specific direction: they design the other person’s evening and leave themselves out of it. The plan says what will happen to your partner. It rarely says what you want to happen to you.
The second under-ask is anticipation. You are Mind-dominant, which means the hours before matter more to you than they do to most people — and you can build those hours deliberately instead of hoping they happen. A message at eleven in the morning does more work than an hour of preparation at night.
There is a third, and it is the one Architects resist hardest: being surprised inside your own structure. Not the plan abandoned — the plan honoured, with one element you did not specify. Some of the best evenings this type has are the ones where the shape held and something inside it was not yours.
What is missing, and where it goes wrong
The failure mode is not cruelty. It is rigidity: the scene stops being a thing happening between two people and becomes a plan being executed on one of them. The tell is that you feel disappointed when your partner does something unscripted — laughs, asks a question, wants something out of order.
That disappointment is the signal to loosen, not to tighten. A plan that cannot absorb a laugh was too tight to begin with. The good version of this type treats the design as a riverbed rather than a railway: it shapes where things go without insisting on the exact path.
There is a quieter version too. Because you think in sequences, you can end up running the same well-designed evening repeatedly without noticing, in the way a good recipe stops being cooking. The tell is that you could describe the last four times in one paragraph. If you can, change one element deliberately — not because the design failed, but because a design you no longer have to think about is no longer doing the thing you enjoy.
What to say
Your instinct is to explain. Resist it. Explanation belongs before, in your own voice; during, the register that suits you is short and declarative.
- “I have already decided what happens tonight. You will find out in order.”
- “Stand there. I am not finished looking at you.”
- “Ask me properly.”
- “Not yet. Ask me again in ten minutes.”
- “That was exactly right. Now the next thing.”
The line most Architects need and least often use is the one that hands something back: “What would you add?” Asked before the evening, not during, it costs the design nothing and changes what the other person brings to it.
Two more that are specific to the way this type runs an evening. One marks a transition, because your scenes have stages and the other person cannot see the plan: “That part is finished. Stand up.” The other ends it deliberately, which matters more for you than for most — an Architect’s scene should close on the design, not on someone running out of energy: “We are stopping here. It went exactly as I wanted.”
Who you play well with
The natural fit is YMIR, The Devotee — also Mind, also Ritual, pointed the other way. Devotees want structure to disappear into, and you produce structure without effort. Expect it to be excellent quickly and to need deliberate variety later, because two Ritual types can settle into a routine so comfortable neither notices it has stopped being a scene.
YMTR, The Cherished is the gentler version of the same pairing and often the better one, because it forces you to build warmth into the design rather than assuming it arrives on its own.
The difficult and interesting pairing is YMIS, The Instigator. They will break your plan on purpose, because being managed is precisely what they enjoy resisting. If you can treat that as part of the design rather than a fault in it, it is the most fun this type has available. If you cannot, you will both be annoyed by eleven.
YBIR, The Stoic is worth considering even though the axes do not obviously match. They are Body where you are Mind, but they share your appetite for structure and they will hold to an agreed shape with unusual seriousness. What you supply is the design; what they supply is someone who takes it as seriously as you do.
Where Architects struggle is with Spontaneous types generally — YBTS, The Melter and YMTS, The Dreamer both want the evening not to have been arranged. That is workable, but it requires you to build the plan and then never mention that a plan exists. Some Architects find that liberating. Others find it unbearable, and it is worth knowing which you are before three months have gone by.
A note on using any of this. A four-letter code is a conversation opener, not a verdict, and the most useful thing you can do with it is hand it to your partner and ask which parts they recognise. Architects in particular are prone to treating the result as a specification — something to be implemented. It is a description of a tendency, and the person you are with will always be better evidence than a quiz. If they read this and say “that is not quite you”, they are probably right and it is worth hearing why.
Where to go next
The two things that extend this type furthest are anticipation and structure, in that order. Denial and delay are the Architect’s natural instruments and they need no equipment at all — building anticipation deliberately is the closest thing to a technical manual for the way you already think.
For the scenes themselves, eighteen scenarios with their setup and escalation is the one to read with a pen. Most of them are sketches rather than scripts, which suits you — you will want to redesign them anyway. When you have the shape and freeze on the words, what to actually say covers the openers.
And if the plan has started to feel like a railway rather than a riverbed, asking what your partner would add is the corrective. It is the conversation this type is best equipped for and least likely to start.