Celebrity Birth Decade Coverage Study

Celebrity Birth Decade Coverage Study: Corpus Size

A fresh disk census on 2026-08-21 located 2,223 JSON files under content/celebrities. Grouping profile.birthData.year by decade yields: 1990s 536, 1980s 533, 1970s 308, 1960s 222, 1950s 136, 2000s 117, 1940s 96, 1930s 49, 1920s 35, 1910s 17, and 1900s 14. These disk-file counts describe repository coverage, not the publish-gated sample or a population. They cannot show that an era produces fame or any BaZi trait. For an individual relevant page, only the recorded birth year is available, not a broader inference from decade totals.

Publish-Gated Sample: Field-by-Field Verification

Any claim about era distribution must first pass a publish-gated check against the repository census. For each celebrity file, confirm profile.birthData.year is present and non-empty; missing or unparseable years exclude the record from decade buckets. Verify the decade label matches the integer year exactly—no rounding or offset. Compare the resulting per-decade counts against the disk-file totals: 1990s 536, 1980s 533, 1970s 308, 1960s 222, 1950s 136, 2000s 117, 1940s 96, 1930s 49, 1920s 35, 1910s 17, 1900s 14. A mismatch indicates a boundary case: duplicate entries, malformed JSON, or files not yet indexed. Because these counts describe repository coverage only, any inference about fame or BaZi traits is unsupported. For foundational terminology, see relevant page.

Celebrity Birth Decade Coverage Study: Birth-Hour Coverage Verification

Treat the 2,223 JSON files under content/celebrities as a raw disk census: each record's profile.birthData.year generates the decade totals (1990s 536, 1980s 533, 1970s 308, 1960s 222, 1950s 136, 2000s 117, 1940s 96, 1930s 49, 1920s 35, 1910s 17, 1900s 14). These counts are repository coverage only. For field-by-field verification, open any file and confirm the presence of profile.birthData.hour; absence means no birth-hour can be asserted. The decade distribution cannot establish which era yields fame or any trait. Boundary case: a file with year 1990 counts in the 1990s group, but without a parsed hour, it contributes nothing to hour-based analysis. See relevant page for chart reading context.

To verify source-field coverage, treat each celebrity file as a record, not a sample of fame. Inspect the JSON at content/celebrities, confirming profile.birthData.year is populated. A valid census date is 2026-08-21; any file modified later falls outside this snapshot. Count files per decade by exact grouping of that year field only. Reject decade totals that aggregate by file creation date, since the packet states disk-file counts describe repository coverage. Boundary case: if a file lacks birthData.year, exclude it from all decade tallies, even if the path suggests a century. No BaZi trait is inferred from counts; day master strength remains unrelated to era totals.

When verifying any era claim, first separate the sample from the population. The packet contains only disk-file counts: 2,223 JSON files under content/celebrities, with profile.birthData.year grouped by decade, led by 1990s at 536 and 1980s at 533. For a boundary case, treat every count as repository coverage, never as a publish-gated sample or as a population. To field-check, confirm that no number is inflated beyond the packet and that no phrase like “era produces fame” appears. The moment a sentence implies a trait or a population, it fails verification. For structural guidance on era boundaries, see relevant page.

Questions the Census Can Answer

The disk census can verify only one claim per file: whether profile.birthData.year exists and which decade it falls into. To check a 1990s count, open each of the 536 matching files and confirm the year string begins with 199; for a 1980s count, confirm 198; and so on down to the 1900s, where 14 files must show 190 through 1909. A boundary case is a file whose year is 1990—it belongs to the 1990s, not the 1980s, because the decade label is inclusive of its first year. If any file lacks profile.birthData.year, it cannot be counted in any decade, so the census total of 2,223 files is not the sum of the decade counts. This procedure answers only coverage questions; it cannot link a decade to a Ten Gods pattern or to fame.

Questions It Cannot Answer

This section cannot answer why a decade dominates, nor whether a BaZi trait causes fame. The packet only gives disk-file counts by profile.birthData.year, and each count is repository coverage, not a publish-gated sample or a population. To verify a boundary case, check every JSON file under content/celebrities and confirm the year field exists, then group by decade without inferring a person's chart. For example, a 1990s file count of 536 only means 536 files are tagged with a 1990s birth year; it says nothing about the era producing fame. The relevant page defines si-zhu terms, but no file count can prove a causal link between a decade and any BaZi outcome. Thus the study remains descriptive, not predictive or explanatory.

Method Replication

A field-by-field verification procedure can replicate this study. First, confirm the disk census date (2026-08-21) and the file count (2,223 JSON files) under content/celebrities. Second, parse each file's profile.birthData.year and bucket by decade. Third, compare the resulting decade counts against the packet values: 1990s 536, 1980s 533, 1970s 308, 1960s 222, 1950s 136, 2000s 117, 1940s 96, 1930s 49, 1920s 35, 1910s 17, and 1900s 14. Boundary cases include missing birthData, non-integer years, or files outside the celebrities folder. These disk-file counts describe repository coverage only; they cannot show that an era produces fame or any BaZi trait.

To treat an entry as countable, open each celebrity JSON under content/celebrities and verify three fields. First, confirm that profile exists and is an object. Second, confirm that profile.birthData exists and is an object. Third, confirm that profile.birthData.year exists and is a number. Only records satisfying all three checks enter the decade buckets listed in the packet. Boundary cases are decided by the stored integer, not by calendar nuance: a file with year 1999 belongs to the 1990s bucket, while year 2000 belongs to the 2000s bucket. The counts 536, 533, 308, 222, 136, 117, 96, 49, 35, 17, and 14 are therefore counts of JSON files meeting these field-presence and numeric-year conditions on the census date 2026-08-21, not counts of any broader gated sample or population.

Data-Quality Limits

A field-by-field verification procedure must begin with the raw disk census of 2,223 JSON files under content/celebrities, since this count defines the repository’s coverage, not any publish-gated sample or population. Grouping profile.birthData.year by decade yields the following boundary cases: 1990s 536, 1980s 533, 1970s 308, 1960s 222, 1950s 136, 2000s 117, 1940s 96, 1930s 49, 1920s 35, 1910s 17, and 1900s 14. Each decade count must be checked against the total files to confirm no missing or duplicated entries, and every file must contain a valid profile.birthData.year before any grouping. The decade labels do not imply that an era produces fame or any BaZi trait; they only partition the raw coverage. Verification therefore stops at the file count and year field, without inferring population trends.

Celebrity Birth Decade Coverage Study: Reader Fact Check

Verify each era claim against the disk census dated 2026-08-21. First, confirm the file count: 2,223 JSON files under content/celebrities. Then, for a given decade, open a sample of profiles and check that profile.birthData.year falls within the stated range. For example, a file counted in the 1980s must have a birth year from 1980 through 1989; otherwise, the grouping is incorrect. Next, re-tally the decade counts from the raw files: 1990s 536, 1980s 533, 1970s 308, 1960s 222, 1950s 136, 2000s 117, 1940s 96, 1930s 49, 1920s 35, 1910s 17, 1900s 14. Ensure these match the article. Finally, note that these counts describe repository coverage only. They cannot be used to prove that an era produces fame or any BaZi trait. If the article implies such a causal link, flag it as unsupported by the packet. No other data should appear.

Celebrity Birth Decade Coverage Study: Conclusion Limits

All counts above are disk-file counts from a single census on 2026-08-21, not a publish-gated sample. They describe repository coverage only. Verify each field as follows: existence of the JSON file confirms a record was present; the decade field must be derived from profile.birthData.year, and no other field may be used to assign a decade. If profile.birthData.year is missing, malformed, or not a four-digit integer, exclude the file from the decade distribution without imputation. If a file appears but its content cannot be parsed as a celebrity profile, exclude it and report a parse failure. The numbers 1990s 536, 1980s 533, 1970s 308, 1960s 222, 1950s 136, 2000s 117, 1940s 96, 1930s 49, 1920s 35, 1910s 17, 1900s 14 are raw file counts, not population estimates. They cannot show that an era produces fame or any BaZi trait.

Celebrity Birth Decade Coverage Study: Corpus Size

To verify corpus size from disk, count JSON files directly under content/celebrities, then group by the year field inside profile.birthData.year. A boundary case arises when the year is missing or non-numeric; such files must be excluded from every decade bucket before totals are reported. Because the disk census is a repository coverage metric, not a publish-gated sample or a population, no decade count can be interpreted as evidence that an era produces fame or any BaZi trait. The only valid conclusion is that the 1990s and 1980s buckets are the largest on disk, with 536 and 533 files respectively, while the 1900s bucket is the smallest at 14. Any comparison beyond these raw file counts exceeds the packet.

To verify the publish-gated sample, begin with the raw disk census: 2,223 JSON files under content/celebrities on 2026-08-21. Each file’s profile.birthData.year yields a decade, producing counts per decade—1990s 536, 1980s 533, 1970s 308, 1960s 222, 1950s 136, 2000s 117, 1940s 96, 1930s 49, 1920s 35, 1910s 17, 1900s 14. These are disk-file counts, not the publish-gated sample. A boundary case arises when a profile exists on disk but is not published; such a file would be counted in the census yet absent from the publish-gated sample, so the sample may exclude it. The comparison is strictly between two repository scopes, with no claim about fame or BaZi traits.