Chinese Fortune-Telling Methods: Engine Scope and Limits

Chinese Fortune-Telling Methods: Engine Scope and Limits: Verified Field Ledger

DeepOracle's public engine computes a verified field ledger: four pillars, stem and branch interactions, pillar interactions, strength, pattern, useful-god lenses, shensha, luck cycles, and annual, monthly, daily, and hourly ladders. It also performs lunar conversion, cross-chart interactions, and timing ratings. The engine does not provide bone-weight calculation, naming recommendations, exam-result prediction, or deterministic event prediction. These unsupported requests are not computable fields. The same relevant page exposes the computed chart; no extra prediction service is attached.

Before interpreting a BaZi chart, confirm every field aligns with its pillar position. The engine's four-pillar computation requires exact inputs: year, month, day, and hour. A misplaced birth hour shifts the hour pillar and its luck ladder; a wrong date alters the day stem and branch. Cross-check the lunar conversion, as solar dates differ from lunar dates in borderline cases. Once the pillars are set, review the interactions—stem combinations, branch clashes, and hidden stems—against the pattern and useful-god lenses. Compare computable fields like strength, shensha, and timing ratings with unsupported requests such as bone-weight or exam prediction. For pillar basics, see relevant page.

Chinese Fortune-Telling Methods: Engine Scope and Limits: Same-Chart Interaction Comparison

To verify a chart, compare the same requested field against both a computable interaction and an unsupported one. The engine exports four pillars, stem/branch/pillar interactions, strength, pattern, useful-god lenses, shensha, luck cycles, time ladders, cross-chart interactions, lunar conversion, and timing ratings. For a boundary case, ask for a bone-weight calculation or naming recommendation: those requests have no engine export, so no comparison can run. Only fields listed in the export scope can produce a same-chart interaction comparison. See how to read a BaZi chart for the computable procedure.

To verify strength and pattern fields, first confirm the public engine returns a strength assessment and a named pattern. These fields are computed from stem, branch, and pillar interactions, not from bone-weight or other unsupported calculators. A boundary case: if a request asks for exam-result prediction, the engine will not supply that because deterministic event prediction is outside scope. Instead, the strength and pattern remain structural outputs for interpretation. For further details on how day-master conditions shape strength, see relevant page.

Luck-Cycle Record: A Field-by-Field Boundary Check

To verify a luck-cycle record in DeepOracle, audit fields in order. First, confirm the four-pillar computation exists; absent pillars invalidate any cycle. Next, check that stem, branch, and pillar interactions are present—these drive the strength and pattern fields, which must be populated. Verify the useful-god lenses appear, as they filter which cycles matter. Shensha markers should be listed for each cycle. Luck cycles and annual, monthly, and daily ladders must each be present; a missing time ladder breaks the record. Cross-chart interactions and lunar conversion are required only if the engine was run with those options. Timing ratings must be attached to each cycle. Any field requesting bone-weight, naming, exam-result, or deterministic event prediction should be flagged as unsupported. For full cycle details, see relevant page.

Field-by-field, the verification procedure for other reported labels is straightforward. Begin with four pillars, stems, branches, and their interactions. Confirm strength, pattern, useful-god lenses, and shensha. Check luck cycles, annual, monthly, daily, and hourly ladders, cross-chart interactions, and lunar conversion. Timing ratings complete the engine's scope. When a label requests bone-weight calculation, naming recommendations, exam-result prediction, or deterministic event prediction, mark it unsupported. Compare each requested field against the public engine's exports. If a field is absent from the engine, it is outside the verified boundary. Consult the relevant page for terminology. No additional mechanism is claimed.

Chinese Fortune-Telling Methods: Engine Scope and Limits: Missing-Capability Inventory

To verify a feature request against the public engine, compare the requested field with the exported computation list. The engine exports four-pillar computation, stem/branch and pillar interactions, strength, pattern, useful-god lenses, shensha, luck cycles and annual/month/day/hour ladders, cross-chart interactions, lunar conversion, and timing ratings. If a request falls outside these fields—such as bone-weight calculation, naming recommendations, exam-result prediction, or deterministic event prediction—the engine does not provide it. For each unsupported request, document the absence in the glossary entry for relevant page, noting that the engine’s scope covers computable fields only; comparisons with unsupported requests must not invent facts about other methods. This field-by-field boundary check prevents unsupported claims from entering the article.

Chinese Fortune-Telling Methods: Engine Scope and Limits: Verifiable Versus Non-Verifiable Claims

To verify a field, check it against the engine’s exported functions. Four pillars, stem/branch/pillar interactions, strength, pattern, useful-god lenses, shensha, luck cycles, lunar conversion, cross-chart interactions, and timing ratings are computable. A claim that references these is verifiable. A claim that requests bone-weight calculation, naming recommendations, exam-result prediction, or deterministic event prediction is not verifiable, because the engine does not export those capabilities. When a field lies outside the exported set, treat it as a boundary case: the engine cannot confirm or refute it. The procedure is to map each claim to an exported function or mark it unsupported. Do not infer a hidden mechanism. Only exported fields can be checked against the engine’s output.

Reader Audit Procedure: Confirming Supported Fields Against Unsupported Requests

To audit this article, treat every claim as a field in a verification table. For each field, ask: does the claim map to an export of the public engine? Confirmed exports are four-pillar computation; branch, stem, and pillar interactions; strength; pattern; useful-god lenses; shensha; luck cycles; annual, month, day, and hour ladders; cross-chart interactions; lunar conversion; and timing ratings. If a field references bone-weight calculation, naming recommendations, exam-result prediction, or deterministic event prediction, mark it as unsupported. A boundary case: a statement comparing a computable field such as strength with an unsupported request like naming is permissible only if it explicitly labels the latter as outside engine scope. No additional fact, mechanism, or hypothetical chart is authorized.

Input-to-Output Comparison: Mapping Requests to Engine Capabilities

To verify scope, compare each input field against the engine's known exports. The engine computes four pillars from birth data, then derives stem, branch, and pillar interactions; strength; pattern; useful-god lenses; shensha; luck cycles; and annual, monthly, daily, and hourly ladders. It also handles lunar conversion, cross-chart interactions, and timing ratings. If a request asks for bone-weight calculation, naming recommendations, exam-result prediction, or deterministic event prediction, the engine has no corresponding output; such fields are unsupported. A boundary case arises when a user inputs birth data expecting a single predictive statement. The engine instead returns a structured set of computable fields, each verifiable against its own module. Thus, field-by-field comparison distinguishes supported calculations from unsupported requests without inventing facts about other methods.

Reader Fact-Check Procedure: Engine Scope and Boundary Cases

To verify the article, list the public engine's exports and compare them with the article's claims. Confirm that it computes four pillars, stem/branch/pillar interactions, strength, pattern, useful-god lenses, shensha, luck cycles, time ladders, cross-chart interactions, lunar conversion, and timing ratings. For each feature mentioned, check if it appears among these exports; if not, mark the claim as unsupported. Boundary cases: requests for bone-weight calculation, naming recommendations, exam-result prediction, or deterministic event prediction are outside the verified scope. Comparisons between computable fields and unsupported requests are allowed only when clearly presented as contrasts, not as implied capabilities. Ensure no invented facts about other methods appear. Finally, confirm that all statements come solely from the allowed evidence; if any sentence introduces a mechanism, hypothetical chart, or life meaning not in the evidence, remove it.## Conclusion: Limits of the Engine A verification procedure checks each requested field against the engine's exports. Four pillars, stem and branch interactions, strength, pattern, useful-god lenses, shensha, luck cycles, time ladders, cross-chart interactions, lunar conversion, and timing ratings are computable. Bone-weight calculation, naming recommendations, exam-result prediction, and deterministic event prediction are unsupported. A boundary case: if a chart includes only a birth date, the engine can compute pillars but cannot output a naming recommendation. Thus, every output must map to an exported function; otherwise, it is outside this article's scope.

Chinese Fortune-Telling Methods: Engine Scope and Limits: Verified Field Ledger

Each field in the public engine undergoes a boundary check against the verified scope. Four-pillar computation, stem/branch/pillar interactions, strength, pattern, useful-god lenses, shensha, luck cycles and annual/month/day/hour ladders, cross-chart interactions, lunar conversion, and timing ratings are all computable. In contrast, bone-weight calculation, naming recommendations, exam-result prediction, and deterministic event prediction are flagged as unsupported requests. The verification procedure records whether an input maps to a computable field or falls outside the ledger. This field-by-field audit prevents scope drift and keeps the engine's outputs within the documented boundary.