HOW TO READ PURPLE STAR DECISION MODEL // ENGLISH MODE

Purple Star, but make it operational.

Think of the Purple Star Decision Model as a systems dashboard for people: role design, pressure points, leverage lanes, and failure modes.

Note: although often described as a “mystic system,” modern interpretation usually treats it more like a pattern-based statistical and psychological framework, not an all-powerful scientific predictor.

1) PRECISION MACHINE

BaZi is like a compact profile. The Purple Star Decision Model is the full control panel.

100+ stars across 12 palaces means it can split life into operating domains: money pattern, work behavior, social leverage, relationship dynamics, timing risk.

Translation: less “you are this type,” more “this subsystem fails here unless you do this.”

2) EX-ROYAL PLAYBOOK

Historically it sat in imperial hands for a reason: it was used for power, not vibes.

The name itself tells the story. Zi Wei is the emperor star, the center node in the map.

In modern terms: this was originally a governance tool before it became your career read.

3) TIMING IS THE WEAPON

The Four Transformations system (Lu 禄, Quan 权, Ke 科, Ji 忌) turns the chart from static profile into moving timeline.

That is why this model can answer not just "what", but also "when" and "through which channel".

It's the difference between “you can win” and “you can win this quarter if you stop playing pretty.”

4) HUMAN-READABLE SYMBOLS

Stars are archetypal and concrete: Tan Lang 贪狼 (desire/network), Wu Qu 武曲 (execution/numbers), Tian Ji 天机 (strategy/systems).

That makes modern questions easier to answer: who you are in a system, and which social role you default to under pressure.

Not “your destiny.” More like “your recurring operating pattern.”

CHART DETAILS GUIDE

Want the full decoder for all domains? Use the chart details page and drill down palace by palace.

See All Areas
FOR NERDS // ENGINE SPEC
Computation Pipeline
birth_input
  -> calendar_normalization
  -> palace_branch_map
  -> major_star_placement
  -> brightness_lookup (M/W/D/L/X)
  -> four_transformations (Lu/Quan/Ke/Ji)
  -> identity_execution_matrix
  -> verdict_renderer
Data Model
chart {
  palaces[12] {
    branch
    stars[]
    transformations[]
  }
  identity
  execution
  verdict
}
Determinism Boundary
  • Deterministic: placement, brightness lookup, transformation state, tier routing.
  • Generative: wording layer only (tone and phrasing).
  • Guardrails: schema checks, polarity checks, fallback paths.
Known Failure Modes
  • School/profile variance in star-state mappings.
  • Ambiguous input terms in object/semantic mapping.
  • Generative tone drift if constraints are weak.
  • Overfitting to one issue bucket tone.
Versioning
  • Track mapping table version IDs.
  • Track verdict override profile version.
  • Log prompt revisions separately from engine revisions.
  • Treat wording updates as non-logic patches.