The Cheng Gu Weight Table: How It Works, and How It Differs from BaZi

Bone Weight Divination and Four Pillar Engine Limits: Verified Field Ledger

A ledger check against the public DeepOracle engine on 2026-08-21 establishes what is and is not exported. The engine exports four-pillar computation, including branch, stem, and pillar interactions; strength and pattern analysis; useful-god lenses; shensha; luck cycles with annual, monthly, daily, and hourly ladders; cross-chart interactions; lunar conversion; and timing ratings. It does not export a bone-weight calculator. No 称骨 lookup or result is available. This means no bone-weight table, formula, range, units, authorship, verses, or gender rules are provided. The only safe comparison is that four-pillar output and lunar conversion are present while bone-weight output is absent. For verified four-pillar and lunar data, see the relevant page.

Bone Weight Divination and Four Pillar Engine Limits: Input and Pillar-Position Check

Before trusting any interpretation, audit the raw inputs against the four-pillar output. The public DeepOracle engine accepts a birth date and time; it publicly exports four-pillar computation and lunar conversion, so a sound check begins there. Confirm the lunar date agrees with the Gregorian input, then verify each pillar’s branch and stem match the expected sexagenary position for the reported year, month, day, and hour. Because the engine does not export a bone-weight calculator, any 称骨 lookup, table, formula, range, units, authorship, verse, or gender rule is a boundary case: such output cannot be produced by the public engine and should be treated as absent. When a reading claims bone-weight results, reject it as outside the verified boundary. For a full orientation to pillar basics and input conventions, see the relevant page.

To verify the same-chart interaction boundary in DeepOracle, open relevant page and inspect the engine's public exports. Field by field, note that four-pillar computation, branch–stem interactions, pillar interactions, strength, pattern, useful-god lenses, shensha, luck cycles, annual/month/day/hour ladders, cross-chart interactions, lunar conversion, and timing ratings are all present. Now search for a bone-weight calculator or 称骨 result: it is absent. There is no bone-weight table, formula, range, units, authorship, verses, or gender rules exported. The comparison is strictly binary: the engine provides four-pillar output and lunar conversion, but no bone-weight lookup or result. Do not infer a hidden 称骨 feature. The absence is a negative capability boundary, not a gap to be filled.

Strength and Pattern Fields: A Boundary Verification

When checking a DeepOracle four-pillar reading, two computed fields—strength and pattern—must be present. The engine exports both, but no bone-weight field appears anywhere in the public API. A verification procedure can confirm this boundary directly: call the four-pillar computation, then search the returned object for a bone-weight key or score. It will be absent. Strength and pattern appear as structured outputs derived from stem, branch, and pillar interactions. In contrast, a 称骨 (bone-weight) result—if one existed—would require its own lookup table, formula, and gender rules. Since the engine exports only four-pillar computation and lunar conversion, any claim of a bone-weight result is unsupported. See relevant page for how strength and pattern are interpreted without a bone-weight extension.

To verify a luck-cycle record against DeepOracle, begin by requesting the four-pillar computation and lunar conversion. Confirm that the returned record includes branch and stem interactions, strength, pattern, useful-god lenses, shensha, and timing ratings for annual, monthly, daily, and hourly ladders. Cross-chart interactions must be present, but no bone-weight calculator, naming recommender, exam-result predictor, or deterministic event predictor should appear. If any 称骨 lookup, result, table, formula, range, units, authorship, verses, or gender rules are returned, treat them as unsupported. The only acceptable comparison is that four-pillar output and lunar conversion are present while bone-weight output is absent. For additional context on luck pillars and their application, see relevant page.

Bone Weight Divination and Four Pillar Engine Limits: Other Reported Labels: A Field-by-Field Boundary Check

When a description mentions “称骨歌”, “袁天罡称骨”, or “bone-weight chart”, verify each reported label against the engine’s exported surface. The public DeepOracle engine exports four-pillar computation and lunar conversion, but it does not export a bone-weight calculator. A reported field such as “bone weight in liang” is therefore absent from the output; a reported field such as “lunar date conversion” is present. Do not infer the presence of a bone-weight table, formula, range, units, authorship, verses, or gender rules from any adjacent label. For interactions among reported labels that do exist, such as the ten gods derived from stem relations, check that they arise from four-pillar output rather than from a bone-weight result. This boundary procedure keeps each label tied to an actual exported capability, with no imported 称骨 content.

Missing-Capability Inventory: Bone Weight Fortune Telling

To verify the boundary of DeepOracle’s public engine, conduct a field-by-field check against the expected features of a bone-weight system. First, attempt to locate any exported function for 称骨 calculation; the engine exposes four-pillar computation (branch, stem, pillar interactions) and lunar conversion, but no such calculator exists. Second, inspect the core index for tables, formulas, or verse mappings; only shensha, luck cycles, and timing ratings are present. Third, test for gender-specific weight rules or unit ranges; none are exported. Fourth, confirm that no naming recommender or exam-result predictor appears. The absence of every bone-weight field is consistent: the engine provides four-pillar output and lunar conversion, but omits all bone-weight artifacts. Any claimed lookup would require an external, non-exported module.

To verify any claim, separate what the public engine actually exports from what it does not. A field-by-field check against lib/bazi-engine/index.ts confirms that four-pillar computation and lunar conversion are present: branch, stem, pillar interactions, strength, pattern, useful-god lenses, shensha, luck cycles, annual/month/day/hour ladders, cross-chart interactions, and timing ratings. None of these fields include a bone-weight calculator, naming recommender, exam-result predictor, or deterministic event predictor. Therefore, any statement about 称骨 lookup, result, table, formula, range, units, authorship, verses, or gender rules is non-verifiable within this engine and must be marked absent. The only safe comparison is that four-pillar output and lunar conversion exist while bone-weight output does not.

To audit this article, a reader may verify the stated capability boundary field by field. First, confirm that the cited engine export list includes four-pillar computation and lunar conversion; in the packet, these are present. Second, check for any exported bone-weight calculator, lookup, or result; the packet confirms none is exported. Third, test whether the article invents a table, formula, range, units, authorship, verses, or gender rules for bone weight; it must not. Fourth, ensure the comparison remains limited to presence of four-pillar output and lunar conversion versus absence of bone-weight output. Fifth, reject any claim that DeepOracle predicts outcomes, names, or exams; the packet prohibits such exports. Finally, scan for interactive-tool or prediction-service framing; the section must remain purely descriptive. If any field fails, the article exceeds the verified boundary.

Bone Weight Divination and Four Pillar Engine Limits: Input-to-Output Comparison

To verify boundary behavior, compare the public engine’s input-to-output mapping against a hypothetical bone-weight service. The engine accepts a birth date and time; after lunar conversion and four-pillar computation, it returns stems, branches, pillar interactions, strength, pattern, useful-god lenses, shensha, and luck ladders. Each output field is traceable to an exported function. A 称骨 lookup, by contrast, would map the same input to a single weight and verse. Since no bone-weight calculator is exported, no such output exists. Any bone-weight result is therefore absent from the public interface; the only safe comparison is that four-pillar output and lunar conversion are present, while bone-weight output is not. Do not infer a table, formula, or gender rule from this absence.

Bone Weight Divination and Four Pillar Engine Limits: Verification Procedure

To verify the boundary of the public DeepOracle engine, perform the following checks in order:

1. Check for a bone-weight calculator export—absent.
2. Check for four-pillar computation export—present.
3. Check for lunar conversion export—present.
4. Check for any bone-weight table, formula, range, units, authorship, verses, or gender rules—absent.

The only safe comparison is that four-pillar output and lunar conversion are present while bone-weight output is absent. No bone-weight lookup or result is supported.

For boundary verification, confirm that the engine does not export a 称骨 lookup, table, formula, range, units, authorship, verses, or gender rules. The engine also does not export naming recommender, exam-result predictor, or deterministic event predictor. Any output claiming a bone-weight result is outside the verified negative capability boundary and must be rejected as unsupported.### Bone Weight Divination and Four Pillar Engine Limits: Verified Field Ledger

A field-by-field boundary check against the public DeepOracle engine yields a clear split. Four-pillar computation is present, including branch, stem, and pillar interactions. Lunar conversion is also present. Bone-weight fortune telling is absent. There is no bone-weight calculator, no 称骨 lookup, and no bone-weight result. The ledger therefore records: four-pillar output, present; lunar conversion, present; bone-weight output, absent. No table, formula, range, units, authorship, verses, or gender rules for bone weight are exported. Any claim of a bone-weight feature in DeepOracle is unsupported by the verified engine surface. The boundary is exact: four-pillar and lunar conversion exist; bone-weight does not.