Famous BaZi Charts Analyzed: Destiny Patterns of Icons

Corpus Size

This repository snapshot, taken on 2026-08-21, contains 2,223 celebrity JSON files on disk, but only 2,017 profiles pass the same chart-integrity publish gate as the live loader. Among these publishable profiles, 47 have a known birth hour, while 1,970 have an unknown hour. Additionally, 1,524 publishable profiles carry a Wikidata QID and at least one Wikidata reference. These counts describe the repository snapshot, not a population sample, and support methodology and data-quality statements only—never BaZi prevalence or life-outcome claims. For details on how these charts are structured and validated, see the relevant page.

To keep the published sample trustworthy, each chart file is gated field by field before it can appear. The loader checks all four pillars, stem-branch pairs, and any optional birth-hour marker against the same integrity rules used for live pages. A file with a missing or malformed field is excluded, even if the celebrity name is famous. Profiles that carry a Wikidata QID and at least one Wikidata reference are also flagged for provenance. This publish gate is mechanical: it does not judge whether a chart is “good” or “bad,” only whether every required field is present and well-formed enough to avoid rendering errors. For readers learning how these fields fit together, see the relevant page.

Birth-hour coverage is a boundary condition, not a headline. The repository census on 2026-08-21 counted 2,223 celebrity JSON files on disk, but only 2,017 passed the chart-integrity publish gate. Among those publishable profiles, just 47 include a known birth hour; the remaining 1,970 have an unknown hour. This gap requires field-by-field verification: a missing hour field means the Four Pillars cannot be completed, and any derived luck cycles or life-timing statements are suspended. The 47 known-hour profiles are the only ones where hour-branch boundary cases can be checked. For method details, see how to read a BaZi chart. The census describes a repository snapshot, not a population sample, so these counts support data-quality statements only.

Source-Field Coverage

Each publishable profile is checked field by field against the repository census. A chart passes only when every required source field is present: known birth hour where available, Wikidata QID, and at least one Wikidata reference. Profiles missing a birth hour still pass if all other fields are complete. The 1,970 unknown-hour profiles are boundary cases—they pass the same integrity gate but cannot support hour-pillar analysis. The 47 known-hour profiles are the only subset eligible for full four-pillar reading. Any profile lacking a QID or reference is excluded, regardless of fame. This procedure controls coverage, not prevalence. See relevant page for how hour pillar affects day-master strength.

Sample Versus Population: A Verification Boundary

Before interpreting any icon's chart, verify the repository's evidentiary boundary. The census counts 2,223 celebrity JSON files on disk, but only 2,017 profiles pass the same chart-integrity publish gate as the live loader. This gate is not a population sample; it is a snapshot filter. For field-by-field verification, treat the publishable set as the sole admissible universe. Among these, 47 profiles have a known birth hour, while 1,970 have an unknown hour. The 1,524 profiles with a Wikidata QID and at least one reference mark the subset where external corroboration is possible. Do not infer prevalence or life outcomes from these counts; they only define which records survive the integrity gate. For methodology on hour-dependent analysis, see the relevant page.

Famous BaZi Charts Analyzed: Destiny Patterns of Icons: Questions the Census Can Answer

A repository census resolves only inventory questions, never interpretive ones. To verify a field, ask: Does this count derive from disk files, publish-gate outcomes, hour presence, or reference presence? Each boundary case matters. For 2,223 JSON files, the first check is whether the chart passes the integrity gate; otherwise it remains raw material, not a publishable profile. Among the 2,017 publishable profiles, the next partition is birth-hour status: 47 with a known hour versus 1,970 with an unknown hour. This distinction limits any hour-dependent analysis, including Ten Gods placement. Finally, 1,524 publishable profiles carry a Wikidata QID and at least one reference—a further filter. Each field is a gate, not a conclusion.

Questions It Cannot Answer
This section cannot resolve interpretive disputes about any listed icon’s fate, character, or fortune. It cannot confirm whether a given BaZi pattern caused a career, illness, relationship, or public outcome. It cannot rank charts by strength, auspiciousness, or destiny quality. It cannot validate external claims about any celebrity’s birth data beyond the repository’s publish gate. It cannot infer prevalence of chart types in a population from the 2,223-file snapshot. For terminology such as the Four Pillars, the section may clarify structural labels (year, month, day, hour) but not their predictive weight. Any statement linking a specific icon’s chart to a life event is outside the allowed factual boundary of this article.

Method Replication: Field-by-Field Verification

To replicate this repository census, an auditor must first run await getAllCelebrities() from lib/content/celebrities.ts on a clone of the 2026-08-21 snapshot, then count JSON files on disk (2,223). Next, apply the identical chart-integrity publish gate used by the live loader: 2,017 profiles pass. Within those, split by birth-hour presence: 47 known, 1,970 unknown. Finally, count publishable profiles carrying both a Wikidata QID and at least one Wikidata reference: 1,524. This procedure describes the snapshot only; no BaZi prevalence or life-outcome inference may be drawn from these numbers.

Counting Definition: Field-by-Field Verification Procedure

To determine whether a profile is “publishable,” each JSON file is checked against a sequence of atomic conditions. Fourth, for the Wikidata reference count, the profile must have a QID string and at least one entry in the references array. A boundary case is a profile with a QID but zero references; it fails the reference condition but may still be publishable if the chart gate passes. The census counts only conditions that are true for each file at the snapshot time, without any interpretation of BaZi meaning.

Famous BaZi Charts Analyzed: Destiny Patterns of Icons: Data-Quality Limits

Before any chart enters analysis, each celebrity JSON file must pass the same chart-integrity publish gate used by the live loader. On 2026-08-21, the repository held 2,223 files, of which 2,017 cleared the gate. The remaining 206 are excluded as a boundary case—not counted as publishable. A second field-by-field verification separates profiles with a known birth hour from those without: 47 publishable profiles have a known hour, while 1,970 have an unknown hour. A third pass checks source depth: 1,524 publishable profiles carry a Wikidata QID and at least one Wikidata reference. These counts describe the snapshot alone; they do not support prevalence or life-outcome statements.

Famous BaZi Charts Analyzed: Destiny Patterns of Icons

A field-by-field verification guards each profile before it is made public. The audit confirms the celebrity JSON file exists on disk, then checks chart-integrity parity against the live loader. For profiles with a known birth hour, the hour field is examined for consistency with the stored BaZi pillars; for unknown-hour cases, the hour is marked absent rather than inferred. The Wikidata QID and at least one reference are required only when a profile claims a Wikidata link. This audit describes repository snapshot conditions, not broader BaZi prevalence or life outcomes.## Conclusion Limits: Boundary Verification

Each field in the repository snapshot requires a documented source before it can be used in any analytic conclusion. A profile with a known hour but no reference fails the integrity gate and must be excluded from publishable counts. The 1,970 publishable profiles with unknown hour define a hard boundary for any statement involving hour-based pillars, regardless of how many total files exist on disk.

Corpus Size: Boundary-Case Verification Procedure

Any claim about the corpus must verifiably match the repository census from 2026-08-21, which counts JSON files and publishable profiles, not a population sample. A boundary case arises when a profile has a known birth hour: only 47 publishable profiles meet this condition. For such a profile, the verification procedure is field-by-field: confirm the hour is present and non-null, confirm the profile passes the same chart-integrity publish gate as the live loader, and confirm it carries a Wikidata QID with at least one Wikidata reference if it is among the 1,524 profiles that do. These checks ensure the counts describe the repository snapshot only.