For the curious
How the math works.
The three wings
The composite is the product of three multiplicative "wings", each anchored to a different aspect of an accountable, whole system:
- Left wing — (S × Sp)C: Somatic foundation (Physical + Nutritional) times the coherence amplifier (Social/Communal), raised to the Conceptual Mastery exponent (mean of all 8 axes). Says: your foundation and your context multiply, and consistency amplifies both.
- Right wing — (T + E)p: Temporal/technological addend plus the environmental addend, raised to the provisional/vocational exponent. Says: adaptation to time and place is additive, and purpose shapes how steeply that compounds.
- Resilience wing — (ER × RS)C/3: Emotional/Relational times Religious/Spiritual, raised to a third of the Conceptual Mastery exponent. Says: relationships and meaning are a separate multiplicative term — independent of foundation and environment, and damped to one-third of C so they don't dominate.
Why multiplicative?
Legacy composites average a handful of items. Averaging lets a high score on one axis mask a collapse on another — so a system can look "fine" while a pillar has failed. This formula is multiplicative because real accountability isn't separable: a deficit in any axis non-linearly reduces the whole. You can't fake a missing pillar to lift the number. As a worked clinical example: a heart-attack survivor with great labs but zero social support does not score "ok" here — the missing axis pulls the whole composite down, exactly as it should.
The consistency exponent
C (Conceptual Mastery) is the mean of all eight axes. It's the exponent on both the left and resilience wings because: when you're consistently strong across the board, C ≈ 10 (in the engine's internal [0, 10] axis-space — see normalization note below) and the wings reflect their honest multiplicative result. When inconsistent and chaotic, C → 0 and the wings approach 1 — but the raw values they sit on are also small, so the overall composite stays low. Consistency rewards the consistent and protects the inconsistent from infinite penalty.
Normalization & log rescaling
For numerical-stability reasons the engine internally operates on axes divided by 10, so each axis enters the formula as a value in [0.0, 10.0] (computed as axis_score / 10; see calculator.js lines 95–119). In this internal space the raw multiplicative result spans from near 0 to about 1040, with the upper bracket established at LOG10_CEIL = 39.68. We then rescale via log₁₀ bracketed to [0, 39.68] and map to [0, 100] for display. The brackets are chosen so all-axes-at-0 displays as 0 and all-axes-at-100 displays as 100, with a meaningful gradient between. The ~1040 figure is the raw upper bound in the engine's [0, 10] internal space, not what you would get by plugging 0–100 values directly into the closed-form formula.
Reference implementation
The function shown here is the same clean-room engine (calculator.js) running live in the health product today — and running right now in your browser: the 41 validation tests below execute locally, with nothing sent to a server. Source: master-equation/calculator.js in the open protocol layer. Test suite: master-equation/calculator.js#runTests() — 41 assertions. Patent-pending — U.S. Provisional 63/921,717.
Want to verify the math yourself? Five ways, all open:
- Run the tests live: click Run validation tests above — all 41 assertions execute in your browser against the loaded calculator code.
- Console it: open your browser's developer console on this page, type
CHMasterEquation.runTests(), press Enter, read the results object.
- Read the open source: the raw JavaScript (~300 lines, unminified, fully commented) is at
calculator.js — view source →. That link opens the plain-text source file — the actual code that runs on this page, served for line-by-line audit.
- Cross-platform parity: the byte-equivalent Python port
calculator.py ships with 50 golden vectors. Both JS and Python must pass every vector to ≤ 0.05 on every commit. Clone the repo and run python3 master-equation/tests/test-golden-vectors.py — 50/50 must pass.
- Recompute it yourself: the 41 in-browser tests and the 50 golden vectors run locally in your own browser — open your developer tools or the test panel above and watch them execute against this page's loaded engine. The clean-room SHA3 and the engine itself are open and readable, so you can recompute any result by hand. See Verify it yourself →.
Sub-signals & action map: every action that moves the equation is declared in
sub-signals.yaml
(measurable signals across the eight axes) and
action-axis-map.yaml
(every action → which signal(s) it updates, with fraud controls). No movement happens outside this contract.