What this page can establish
This article explains accuracy and limits from the versioned implementation boundary. accuracy is not a single score in the implementation. The repository separately records input precision, rule set, provenance, fixture review status, warnings, and documented method differences. It does not add traditional interpretation that is absent from the repository sources.
Independent example
The timezone-difference fixture retains IANA provenance while noting that iztro has no native timezone input. The example demonstrates a limitation that must remain visible beside output.
Figure specification
Figure 9: an evidence panel mock with input precision, ruleSetId, timezone provenance, warnings, and fixture review state. 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.




