What this page can establish
This article explains life, body, and configuration fields from the versioned implementation boundary. the normalized contract stores soulPalaceId and bodyPalaceId as identifiers that must resolve to existing palace entries. Transformations are a separate array of star and transformation identifiers. It does not add traditional interpretation that is absent from the repository sources.
Independent example
In the leap-month fixture, life and body identifiers point to different recorded branches. The example shows that the fields can differ without assigning either field a personal meaning.
Figure specification
Figure 6: a field map showing soulPalaceId, bodyPalaceId, transformations, and their referenced palace or star identifiers. The figure is an explanatory diagram, not a generated natal chart and not an instruction to make a personal decision.
Limits
The current application uses iztro 2.6.0 with ziwei.default, preserves input precision and warnings, and records documented gaps. It does not independently validate true-solar-time correction, every school variation, or traditional meanings outside the mapped fields.
Continue
Build a Tu Vi chart, Tu Vi knowledge hub, first related article, second related article.




