MBTI compatibility, read against a Western birth chart

A pair reading is two single-person readings joined at the resonance band. We run the four-system engine on each person independently, then look at the produced spines against each other. The intersections that name a friction or an opposition on a single chart are the same names a pair compatibility reading uses for cross-chart friction.

This is the answer to a frequent question: does my Myers-Briggs type clash with my partner’s Sun sign? It depends on the single-chart intersection table. If the chart-type intersection fires a named friction, the answer is “yes, by structure, under shared conditions”. If not, no engine-named friction is produced, and the prose can talk about whatever else it finds.

The engine doesn’t claim MBTI equals astrology, and it doesn’t claim the two systems agree all the time. It claims they call the same move by different names when they happen to. A compatibility reading uses those calls to produce the report.

The clearest engine-named friction is Fire-dominant chart × Water-element year. A chart whose dominant element is Fire pushes heat and outward motion; a year whose element is Water cools, contains, and flows around. The named intersection has been tagged Fire vs. Water.

A 1996 Lisbon chart (April 15, INFP) puts the dominant element Fire (an Aries Sun rises to Fire-dominant modality); 1996 is a Water-Rat year. The engine fires Fire vs. Water. The chart’s instinctive outward motion in 1996 runs against the year’s flow-around and contain. It is not a curse. It is a named structural friction that tells the year’s reading to acknowledge what the chart will ask of it.

The INFP preference (I-dominant, N-leaning) overlays that. A private, pattern-seeking person whose chart is asking them to push outward into a year that wants to contain — the report names this matrix correctly because the four systems feed it four different slices of the same year.

Single-chart readings treat each person in isolation. Two charts, run through the same engine independently, give two reading recommendations. Compatibility runs those recommendations against each other in one artifact.

The pair report asks the engine to surface every named intersection present in either chart, then annotate which of those intersections are present in both charts (and which intensify, fade, or invert when run together). Frictional intersections that are aligned — chart-1 and chart-2 both have Fire vs. Water as their dominant rhythm — produce a different advice than frictional intersections that are oppositely structured.

For most readers, the practical question is whether the named resonances in one person’s reading match, oppose, or amplify the named resonances in the other person. The answer is in the same engine output the single-chart reading uses; only the comparison is new.

Single readings are best when the question is about one person’s year and one person’s chart dominates the narrative. Pair readings are best when the question involves two people’s charts engaging each other, especially across a year’s pattern. A pair reading won’t fix a single-chart question; a single reading won’t pick up cross-chart friction.

If one of the parties has not yet taken their intake, treat the compatibility surface as a starting point — the unified engine cannot produce a useful pair spine without both inputs. The free preview feed runs on the single-person intake; the paid pair-reading surface runs only after both inputs exist.

The free preview at the foot of this page is single-person and runs the same engine on you. Once both your partner and you have a free preview, the pair surface picks up the cross-chart spine in one artifact.