How to read the Sukuyo compatibility table
A Sukuyo compatibility table needs a source mansion, target mansion, and direction. Each of the 27 mansion pages supplies one two-way row.
Overview
The reverse row should swap roles while preserving the family. Check a known pair before interpreting an unfamiliar cell.
At a glance
- Roster size
- 27
- Ordered pairs
- 729
- Diagonal
- 命 in both directions
Choose the row owner
Open the page for the reference person’s mansion. Locate the other person’s mansion in its relationship section.
The row explicitly provides both the forward label and the reverse label.
Check a simple example
On the 昴 page, 畢 is 榮 from 昴 and 親 in reverse. On the 畢 page the directions swap.
The family stays 榮親; this provides a quick orientation check.
Do not confuse ordinals and offsets
The source mansion is inclusive position one but offset zero. Position ten is offset nine.
Mixing the two conventions produces a one-position error throughout the table.
Understand the diagonal
A mansion compared with itself returns 命 in both directions. It is one of the 729 ordered pairs.
The table describes identifiers, not 729 independent kinds of human relationship.
Use the result with context
Keep the birth-mansion calculation evidence with the table entry. A lookup can be correct while the original birthday is uncertain.
Use actual observations to discuss the relationship; a cell does not contain a compatibility percentage.
Audit a table row
For one source mansion, confirm that all 27 targets appear once, that the diagonal is 命 and that each reverse value agrees with the target mansion’s row.
A complete row verifies table consistency. It does not turn 729 ordered cells into measured probabilities or independent relationship types.
Sources and editorial basis
- 宿曜經 · T1299 卷下卷下「三必祕要法」example beginning 畢: inclusive counting and repeated roles.The three-nine passage supplies historical relative-position terminology. It is not evidence that a modern relationship outcome is determined by a mansion pair.
- OpenFate Sukuyo calculator and calculation conventionEditorial code check 2026-09-10, policy 1.0.0: matrix; policy.ts, constants.ts, engine.ts and traditional-cycles.ts. Product settings are not an independent historical authority; practical examples are OpenFate editorial applications.Product-specific input and output reference. Editorial checks also inspected policy 1.0.0 and the month-start constants on 2026-09-10; those implementation checks are not an independent traditional authority.