Pattern Sources, Aliases, and Limits: Evidence-Led Guide
Pattern Sources, Aliases, and Limits: chart evidence, source conditions, method, example, near miss, variants, and limits.
Overview
Pattern Sources, Aliases, and Limits covers normalizing competing names while preserving edition, school, rule version, source locator, and interpretation boundary. Start with the calculated chart record and cited source condition, then compare the worked example with the near miss before making an interpretation.
At a glance
- Canonical scope
- normalizing competing names while preserving edition, school, rule version, source locator, and interpretation boundary
- Deterministic evidence
- OpenFate’s reviewed pattern registry preserves source tags, registry version, duplicate-key guards, and localized labels. Canonicalization may join aliases to one key only while retaining edition, school, locator, and rule boundary.
- Verification question and source scope
- For Pattern Sources, Aliases, and Limits, use this verification question: Which mandatory predicate would make the named hit disappear if removed? Keep the answer inside its source boundary: Deterministic evidence ends at the named chart output, exact source condition, and declared rule version. Symbolic meaning remains a revisable interpretation, never a verified event, diagnosis, social rank, or fixed trait.
- Worked example
- Map two spelling variants to one pattern ID, keep both visible aliases, and attach each source locator. If their condition sets differ, assign separate rule versions rather than silently merging them.
- Near miss
- Deleting the source name after normalization, merging homonymous patterns with different predicates, or presenting the preferred alias as the historically original title loses provenance.
- Variant and safety boundary
- Deleting the source name after normalization, merging homonymous patterns with different predicates, or presenting the preferred alias as the historically original title loses provenance. Do not use a chart symbol alone for medical, mental-health, relationship, financial, legal, employment, or safety decisions. Use consent, current records, qualified support, and observable circumstances.
Definition and Scope
Pattern Sources, Aliases, and Limits has one defined scope on this page: normalizing competing names while preserving edition, school, rule version, source locator, and interpretation boundary
A supported reading of Pattern Sources, Aliases, and Limits needs this page-specific evidence: OpenFate’s reviewed pattern registry preserves source tags, registry version, duplicate-key guards, and localized labels. Canonicalization may join aliases to one key only while retaining edition, school, locator, and rule boundary.
- Before interpreting Pattern Sources, Aliases, and Limits, identify the smallest chart record that supports the exact claim.
Chart Evidence and Source Conditions
Apply the Pattern Sources, Aliases, and Limits evidence through this reproducible method: Which mandatory predicate would make the named hit disappear if removed?
The source boundary for Pattern Sources, Aliases, and Limits determines what may be claimed: Deterministic evidence ends at the named chart output, exact source condition, and declared rule version. Symbolic meaning remains a revisable interpretation, never a verified event, diagnosis, social rank, or fixed trait.
Reading Method and Verification Steps
The bounded example applies those conditions without extending the claim: Map two spelling variants to one pattern ID, keep both visible aliases, and attach each source locator. If their condition sets differ, assign separate rule versions rather than silently merging them.
The nearest overreach drops or changes a required condition: Deleting the source name after normalization, merging homonymous patterns with different predicates, or presenting the preferred alias as the historically original title loses provenance.
Worked Example, Near Miss, and School Variants
Keep this documented variant separate when comparing results: When sources or schools disagree on Pattern Sources, Aliases, and Limits, record whether the placement table, geometry definition, pattern threshold, or naming convention changed before comparing results.
Variants, Limits, and Evidence Boundary
The Pattern Sources, Aliases, and Limits interpretation stops at this stated limit: Do not extend Pattern Sources, Aliases, and Limits beyond its calculated evidence, cited source condition, and declared school scope.
Consequential decisions remain outside the Pattern Sources, Aliases, and Limits chart reading: Do not use a chart symbol alone for medical, mental-health, relationship, financial, legal, employment, or safety decisions. Use consent, current records, qualified support, and observable circumstances.
- Use the Pattern Sources, Aliases, and Limits result to choose one observable, reversible next step rather than predicting an outcome.
Complete topic index
Every workbook topic assigned to this canonical page appears at a stable anchor. Each entry records scope, inputs, flags, and alias ownership as an auditable reference—not a standalone interpretation. Duplicate backlog rows resolve to the same anchor instead of creating duplicate URLs.
- Conditions and inputs
- Missing-input rule: if a listed input or verified chart value is unavailable, stop at the definition; do not infer, calculate, or predict the missing value.
- Calculation flag: partial. Some steps are rule-based, but this atom does not establish a complete computed result; verify the page’s stated inputs and interpretive boundary.
- School-variant flag: yes. Apply only under an identified school or calculation policy and compare the alternate rule.
- School-variant flag: sometimes. Check whether the page’s named rule or school condition applies before using this component.
- Category and guidance boundary
- Apply this only under the named calculation or school policy, and compare alternate rules before treating the result as reproducible.
- Source inheritance
- Complete topic index does not assert an atom-specific citation. It inherits this canonical page’s bibliography and locator notes as page-level context only; verify the relevant cited passage before relying on a claim.
Zi Wei Dou Shu Pattern: 格局的古籍來源核對
- Topic-specific scope
- Entity 1: 格局的古籍來源核對
- Conditions and inputs
- Calculation state: Partial
- School-variant state: Yes
- Stable reference
- ZW-PUB-1679
- Inventory classification
- 18 格局資料庫 · 經典與現代格局
Zi Wei Dou Shu FAQ: 格局好是不是一定富貴
- Topic-specific scope
- Named inputs: none recorded.
- Conditions and inputs
- Calculation state: Partial
- School-variant state: Sometimes
- Stable reference
- ZW-PUB-2065
- Inventory classification
- 23 FAQ、案例與排錯 · 使用者問題與驗證
Sources and editorial basis
- iztro 紫微鬥數格局iztro《紫微鬥數格局》「前言」（古籍、網路來源、歷史語境與全盤判讀限制）A public pattern catalogue whose preface distinguishes simplified pattern formulas, source variety, historical social categories, strict conditions, and the need to read the full chart.
- OpenFate Ziwei Pattern Detectorsapp/modules/ziwei/lookup/geju.ts:20–27 and :684–711; source tag, registry version, duplicate-key guard, and localization boundaryVersioned product rules emit formed hits labelled auspicious, breaking, or structural. They do not currently emit a generic near-match or false-pattern result.