Formed, Broken, False, and Near Patterns: Evidence-Led Guide
Formed, Broken, False, and Near Patterns: chart evidence, source conditions, method, example, near miss, variants, and limits.
Overview
Formed, Broken, False, and Near Patterns covers condition-by-condition classification that preserves missing, contradictory, and merely adjacent evidence. 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
- condition-by-condition classification that preserves missing, contradictory, and merely adjacent evidence
- Deterministic evidence
- OpenFate’s reviewed pattern registry, :29–139, and :692–711 currently emits formed hits only. It has no generic broken, false, or near-pattern output, so failed predicates must remain explicit conditions rather than invented classifications.
- Verification question and source scope
- For Formed, Broken, False, and Near Patterns, 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
- If a detector passes three required checks but fails a fourth, record the three passes and one failure. Report no formed hit; only call it “near” when a separately sourced rule defines that category.
- Near miss
- Automatically labelling every failed detector “broken” or “false,” or hiding a contradictory condition to preserve a desired name, adds states the API does not own.
- Variant and safety boundary
- Automatically labelling every failed detector “broken” or “false,” or hiding a contradictory condition to preserve a desired name, adds states the API does not own. 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
Formed, Broken, False, and Near Patterns has one defined scope on this page: condition-by-condition classification that preserves missing, contradictory, and merely adjacent evidence
A supported reading of Formed, Broken, False, and Near Patterns needs this page-specific evidence: OpenFate’s reviewed pattern registry, :29–139, and :692–711 currently emits formed hits only. It has no generic broken, false, or near-pattern output, so failed predicates must remain explicit conditions rather than invented classifications.
- Before interpreting Formed, Broken, False, and Near Patterns, identify the smallest chart record that supports the exact claim.
Chart Evidence and Source Conditions
Apply the Formed, Broken, False, and Near Patterns evidence through this reproducible method: Which mandatory predicate would make the named hit disappear if removed?
The source boundary for Formed, Broken, False, and Near Patterns 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: If a detector passes three required checks but fails a fourth, record the three passes and one failure. Report no formed hit; only call it “near” when a separately sourced rule defines that category.
The nearest overreach drops or changes a required condition: Automatically labelling every failed detector “broken” or “false,” or hiding a contradictory condition to preserve a desired name, adds states the API does not own.
Worked Example, Near Miss, and School Variants
Keep this documented variant separate when comparing results: When sources or schools disagree on Formed, Broken, False, and Near Patterns, record whether the placement table, geometry definition, pattern threshold, or naming convention changed before comparing results.
Variants, Limits, and Evidence Boundary
The Formed, Broken, False, and Near Patterns interpretation stops at this stated limit: Do not extend Formed, Broken, False, and Near Patterns beyond its calculated evidence, cited source condition, and declared school scope.
Consequential decisions remain outside the Formed, Broken, False, and Near Patterns 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 Formed, Broken, False, and Near Patterns 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.
- 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-1596
- Inventory classification
- 18 格局資料庫 · 經典與現代格局
Zi Wei Dou Shu Pattern: 成格、破格與加強條件
- Topic-specific scope
- Entity 1: 成格、破格與加強條件
- Conditions and inputs
- Calculation state: Partial
- School-variant state: Yes
- Stable reference
- ZW-PUB-1597
- Inventory classification
- 18 格局資料庫 · 經典與現代格局
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:13–27, :29–139, and :692–711; current API emits formed hits only, not generic near-match or false-pattern resultsVersioned product rules emit formed hits labelled auspicious, breaking, or structural. They do not currently emit a generic near-match or false-pattern result.