Product foundation

How Core Score Is Formed

See how Myndora builds subdomain core scores from the three core layers, then rolls those smaller signals up into broader domain-level pattern reads.

Quick answer

Trait, Motivation, and Reactivity combine into a subdomain core score. Five subdomain core scores then support a broader domain-level pattern that is easier to interpret and use across the product.

Why this matters

This explains why Myndora keeps the building blocks small and specific first, then uses domain-level patterns as the clearer high-level signal for interpretation and fit.

Start with the subdomain building block

A subdomain core score is the combined read for one subdomain formed from Trait, Motivation, and Reactivity.

It is the foundational signal for one small part of the profile map, not a global personality score and not the highest-level summary a user should rely on by itself.

What goes into one subdomain score

The score combines the three core layers only: Trait, Motivation, and Reactivity.

This keeps the subdomain core score focused on foundational pattern structure rather than mixing in later or unrelated kinds of signal that would blur what the score is describing.

Why the product does not stop at the subdomain

A subdomain score is useful because it isolates one specific recurring pattern. But users usually need a broader read than one small component at a time.

That is why Myndora uses subdomain core scores as building blocks rather than treating them as the final layer of interpretation.

How domain-level pattern is formed

Each domain contains five subdomains. Once those subdomains have core scores, Myndora can combine them into a broader domain-level pattern read.

That broader domain signal is often easier to interpret because it reflects the larger area of functioning instead of only one narrow subdomain inside it.

Why domain-level pattern matters more in practice

Domain-level patterns provide the clearer high-level signal for reading the Living Profile. They make it easier to understand what keeps recurring across a larger part of the map.

They also support product features like Profile Fit, which compares domain-level pattern signals against structured fit targets across work, relationships, and environments.

How to read the hierarchy correctly

Read the subdomain core score as the detail layer: the smaller component that shows one specific recurring pattern. Read the domain-level pattern as the broader signal that pulls several related subdomains into one more usable picture.

Both levels matter. Subdomains provide precision and evidence. Domains provide the broader pattern that is usually easier to interpret, apply, and match against fit conditions across the product.