Files
worldmonitor/tests/resilience-coverage-influence-gate.test.mts
Elie Habib 7cf37c604c feat(resilience): PR 3 — dead-signal cleanup (plan §3.5, §3.6) (#3297)
* feat(resilience): PR 3 §3.5 — retire fuelStockDays from core score permanently

First commit in PR 3 of the resilience repair plan. Retires
`fuelStockDays` from the core score with no replacement.

Why permanent, not replaced:
IEA emergency-stockholding rules are defined in days of NET IMPORTS
and do not bind net exporters by design. Norway/Canada/US measured
in days-of-imports are incomparable to Germany/Japan measured the
same way — the construct is fundamentally different across the two
country classes. No globally-comparable recovery-fuel signal can
be built from this source; the pre-repair probe showed 100% imputed
at 50 for every country in the April 2026 freeze.

  scoreFuelStockDays:
    - Rewritten to return coverage=0 + observedWeight=0 +
      imputationClass='source-failure' for every country regardless
      of seed content.
    - Drops the dimension from the `recovery` domain's coverage-
      weighted mean automatically; remaining recovery dimensions
      pick up the share via re-normalisation in
      `_shared.ts#coverageWeightedMean`.
    - No explicit weight transfer needed — the coverage-weighted
      blend handles redistribution.

  Registry:
    - recoveryFuelStockDays re-tagged from tier='enrichment' to
      tier='experimental' so the Core coverage gate treats it as
      out-of-score.
    - Description updated to make the retirement explicit; entry
      stays in the registry for structural continuity (the
      dimension `fuelStockDays` remains in RESILIENCE_DIMENSION_ORDER
      for the 19-dimension tests; removing the dimension entirely is
      a PR 4 structural-audit concern).

  Housekeeping:
    - Removed `RESILIENCE_RECOVERY_FUEL_STOCKS_KEY` constant (no
      longer read; noUnusedLocals would reject it).
    - Removed `RecoveryFuelStocksCountry` interface for the same
      reason. Comment at the removed declaration instructs future
      maintainers not to re-add the type as a reservation; when a
      new recovery-fuel concept lands, introduce a fresh interface.

Plan reference: §3.5 point 1 of
`docs/plans/2026-04-22-001-fix-resilience-scorer-structural-bias-plan.md`.

51 resilience tests pass, typecheck + biome clean. The
`recovery` domain's published score will shift slightly for every
country because the 0.10 slot that fuelStockDays was imputing to
now redistributes; the compare-harness acceptance-gate rerun at
merge time will quantify the shift per plan §6 gates.

* feat(resilience): PR 3 §3.5 — retire BIS-backed currencyExternal; rebuild on IMF inflation + WB reserves

BIS REER/DSR feeds were load-bearing in currencyExternal (weights 0.35
fxVolatility + 0.35 fxDeviation, ~70% of dimension). They cover ~60
countries max — so every non-BIS country fell through to
curated_list_absent (coverage 0.3) or a thin IMF proxy (coverage 0.45).
Combined with reserveMarginPct already removed in PR 1, currencyExternal
was the clearest "construct absent for most of the world" carrier left
in the scorer.

Changes:

_dimension-scorers.ts
- scoreCurrencyExternal now reads IMF macro (inflationPct) + WB FX
  reserves only. Coverage ladder:
    inflation + reserves → 0.85 (observed primary + secondary)
    inflation only       → 0.55
    reserves only        → 0.40
    neither              → 0.30 (IMPUTE.bisEer retained for snapshot
                                 continuity; semantics read as
                                 "no IMF + no WB reserves" now)
- Removed dead symbols: RESILIENCE_BIS_EXCHANGE_KEY constant (reserved
  via comment only, flagged by noUnusedLocals), stddev() helper,
  getCountryBisExchangeRates() loader, BisExchangeRate interface,
  dateToSortableNumber() — all were exclusive callers of the retired
  BIS path.

_indicator-registry.ts
- New core entry inflationStability (weight 0.60, tier=core,
  sourceKey=economic:imf:macro:v2).
- fxReservesAdequacy weight 0.15 → 0.40 (secondary reliability
  anchor).
- fxVolatility + fxDeviation demoted tier=enrichment → tier=experimental
  (BIS ~60-country coverage; off the core weight sum).
- Non-experimental weights now sum to 1.0 (0.60 + 0.40).

scripts/compare-resilience-current-vs-proposed.mjs
- EXTRACTION_RULES: added inflationStability →
  imf-macro-country-field field=inflationPct so the registry-parity
  test passes and the correlation harness sees the new construct.

tests/resilience-dimension-scorers.test.mts
- Dropped BIS-era wording ("non-BIS country") and test 266
  (BIS-outage coverage 0.35 branch) which collapsed to the inflation-
  only path post-retirement.
- Updated coverage assertions: inflation-only 0.45 → 0.55; inflation+
  reserves 0.55 → 0.85.

tests/resilience-scorers.test.mts
- domainAverages.economic 68.33 → 66.33 (US currencyExternal score
  shifts slightly under IMF+reserves vs old BIS composite).
- stressScore 67.85 → 67.21; stressFactor 0.3215 → 0.3279.
- overallScore 65.82 → 65.52.
- baselineScore unchanged (currencyExternal is stress-only).

All 6324 data-tier tests pass. typecheck:api clean. No change to
seeders or Redis keys; this is a pure scorer + registry rebuild.

* feat(resilience): PR 3 §3.5 point 3 — re-goalpost externalDebtCoverage (0..5 → 0..2)

Plan §2.1 diagnosis table showed externalDebtCoverage saturating at
score=100 across all 9 probe countries — including stressed states.
Signal was collapsed. Root cause: (worst=5, best=0) gave every country
with ratio < 0.5 a score above 90, and mapped Greenspan-Guidotti's
reserve-adequacy threshold (ratio=1.0) to score 80 — well into "no
worry" territory instead of the "mild warning" it should be.

Re-anchored on Greenspan-Guidotti directly: ratio=1.0 now maps to score
50 (mild warning), ratio=2.0 to score 0 (acute rollover-shock exposure).
Ratios above 2.0 clamp to 0, consistent with "beyond this point the
country is already in crisis; exact value stops mattering."

Files changed:

- _indicator-registry.ts: recoveryDebtToReserves goalposts
  {worst: 5, best: 0} → {worst: 2, best: 0}. Description updated to
  cite Greenspan-Guidotti; inline comment documents anchor + rationale.

- _dimension-scorers.ts: scoreExternalDebtCoverage normalizer bound
  changed from (0..5) to (0..2), with inline comment.

- docs/methodology/country-resilience-index.mdx: goalpost table row
  5-0 → 2-0, description cites Greenspan-Guidotti.

- docs/methodology/indicator-sources.yaml:
  * constructStatus: dead-signal → observed-mechanism (signal is now
    discriminating).
  * reviewNotes updated to describe the new anchor.
  * mechanismTestRationale names the Greenspan-Guidotti rule.

- tests/resilience-dimension-monotonicity.test.mts: updated the
  comment + picked values inside the (0..2) discriminating band (0.3
  and 1.5). Old values (1 vs 4) had 4 clamping to 0.

- tests/resilience-dimension-scorers.test.mts: NO score threshold
  relaxed >90 → >=85 (NO ratio=0.2 now scores 90, was 96).

- tests/resilience-scorers.test.mts: fixture drift:
  * domainAverages.recovery 54.83 → 47.33 (US extDebt 70 → 25).
  * baselineScore 63.63 → 60.12 (extDebt is baseline type).
  * overallScore 65.52 → 63.27.
  * stressScore / stressFactor unchanged (extDebt is baseline-only).

All 6324 data-tier tests pass. typecheck:api clean.

* feat(resilience): PR 3 §3.6 — CI gate on indicator coverage and nominal weight

Plan §3.6 adds a new acceptance criterion (also §5 item 5):

> No indicator with observed coverage below 70% may exceed 5% nominal
> weight OR 5% effective influence in the post-change sensitivity run.

This commit enforces the NOMINAL-WEIGHT half as a unit test that runs
on every CI build. The EFFECTIVE-INFLUENCE half is produced by
scripts/validate-resilience-sensitivity.mjs as a committed artifact;
the gate file only asserts that script still exists so a refactor that
removes it breaks the build loudly.

Why the gate exists (plan §3.6):

  "A dimension at 30% observed coverage carries the same effective
   weight as one at 95%. This contradicts the OECD/JRC handbook on
   uncertainty analysis."

Implementation:

tests/resilience-coverage-influence-gate.test.mts — three tests:
  1. Nominal-weight gate: for every core indicator with coverage < 137
     countries (70% of the ~195-country universe), computes its nominal
     overall weight as
       indicator.weight × (1/dimensions-in-domain) × domain-weight
     and asserts it does not exceed 5%. Equal-share-per-dimension is
     the *upper bound* on runtime weight (coverage-weighted mean gives
     a lower share when a dimension drops out), so this is a strict
     bound: if the nominal number passes, the runtime number also
     passes for every country.
  2. Effective-influence contract: asserts the sensitivity script
     exists at its expected path. Removing it (intentionally or by
     refactor) breaks the build.
  3. Audit visibility: prints the top 10 core indicators by nominal
     overall weight. No assertion beyond "ran" — the list lets
     reviewers spot outliers that pass the gate but are near the cap.

Current state (observed from audit output):

  recoveryReserveMonths:   nominal=4.17%  coverage=188
  recoveryDebtToReserves:  nominal=4.17%  coverage=185
  recoveryImportHhi:       nominal=4.17%  coverage=190
  inflationStability:      nominal=3.40%  coverage=185
  electricityConsumption:  nominal=3.30%  coverage=217
  ucdpConflict:            nominal=3.09%  coverage=193

Every core indicator has coverage ≥ 180 (already enforced by the
pre-existing indicator-tiering test), so the nominal-weight gate has
no current violators — its purpose is catching future drift, not
flagging today's state.

All 6327 data-tier tests pass. typecheck:api clean.

* docs(resilience): PR 3 methodology doc — document §3.5 dead-signal retirements + §3.6 coverage gate

Methodology-doc update capturing the three §3.5 landings and the §3.6 CI
gate. Five edits:

1. **Known construct limitations section (#5 and #6):** strikethrough the
   original "dead signals" and "no coverage-based weight cap" items,
   annotate them with "Landed in PR 3 §3.5"/"Landed in PR 3 §3.6" +
   specifics of what shipped.

2. **Currency & External H4 section:** completely rewritten. Old table
   (fxVolatility / fxDeviation / fxReservesAdequacy on BIS primary) is
   replaced by the two-indicator post-PR-3 table (inflationStability at
   0.60 + fxReservesAdequacy at 0.40). Coverage ladder spelled out
   (0.85 / 0.55 / 0.40 / 0.30). Legacy BIS indicators named as
   experimental-tier drill-downs only.

3. **Fuel Stock Days H4 section:** H4 heading text kept verbatim so the
   methodology-lint H4-to-dimension mapping does not break; body
   rewritten to explain that the dimension is retired from core but the
   seeder still runs for IEA-member drill-downs.

4. **External Debt Coverage table row:** goalpost 5-0 → 2-0, description
   cites Greenspan-Guidotti reserve-adequacy rule.

5. **New v2.2 changelog entry** — PR 3 dead-signal cleanup, covering
   §3.5 points 1/2/3 + §3.6 + acceptance gates + construct-audit
   updates.

No scoring or code changes in this commit. Methodology-lint test passes
(H4 mapping intact). All 6327 data-tier tests pass.

* fix(resilience): PR 3 §3.6 gate — correct share-denominator for coverage-weighted aggregation

Reviewer catch (thanks). The previous gate computed each indicator's
nominal overall weight as

  indicator.weight × (1 / N_total_dimensions_in_domain) × domain_weight

and claimed this was an upper bound ("actual runtime weight is ≤ this
when some dimensions drop out on coverage"). That is BACKWARDS for
this scorer.

The domain aggregation is coverage-weighted
(server/worldmonitor/resilience/v1/_shared.ts coverageWeightedMean),
so when a dimension pins at coverage=0 it is EXCLUDED from the
denominator and the surviving dimensions' shares go UP, not down.

PR 3 commit 1 retires fuelStockDays by hard-coding its scorer to
coverage=0 for every country — so in the current live state the
recovery domain has 5 contributing dimensions (not 6), and each core
recovery indicator's nominal share is

  1.0 × 1/5 × 0.25 = 5.00% (was mis-reported as 4.17%)

The old gate therefore under-estimated nominal influence and could
silently pass exactly the kind of low-coverage overweight regression
it is meant to block.

Fix:

- Added `coreBearingDimensions(domainId)` helper that counts only
  dimensions that have ≥1 core indicator in the registry. A dimension
  with only experimental/enrichment entries (post-retirement
  fuelStockDays) has no core contribution → does not dilute shares.
- Updated `nominalOverallWeight` to divide by the core-bearing count,
  not the raw dimension count.
- Rewrote the helper's doc comment to stop claiming this is a strict
  upper bound — explicitly calls out the dynamic case (source failure
  raising surviving dim shares further) as the sensitivity script's
  responsibility.
- Added a new regression test: asserts (a) at least one recovery
  dimension is all-non-core (fuelStockDays post-retirement),
  (b) fuelStockDays has zero core indicators, and (c) recoveryDebt
  ToReserves nominal = 0.05 exactly (not 0.0417) — any reversion
  of the retirement or regression to N_total-denominator will fail
  loudly.

Top-10 audit output now correctly shows:

  recoveryReserveMonths:   nominal=5%     coverage=188
  recoveryDebtToReserves:  nominal=5%     coverage=185
  recoveryImportHhi:       nominal=5%     coverage=190
  (was 4.17% each under the old math)

All 486 resilience tests pass. typecheck:api clean.

Note: the 5% figure is exactly AT the cap, not over it. "exceed" means
strictly > 5%, so it still passes. But now the reviewer / audit log
reflects reality.

* fix(resilience): PR 3 review — retired-dim confidence drag + false source-failure label

Addresses the Codex review P1 + P2 on PR #3297.

P1 — retired-dim drag on confidence averages
--------------------------------------------
scoreFuelStockDays returns coverage=0 by design (retired construct),
but computeLowConfidence, computeOverallCoverage, and the widget's
formatResilienceConfidence averaged across all 19 dimensions. That
dragged every country's reported averageCoverage down — US went from
0.8556 (active dims only) to 0.8105 (all dims) — enough drift to
misclassify edge countries as lowConfidence and to shift the ranking
widget's overallCoverage pill for every country.

Fix: introduce an authoritative RESILIENCE_RETIRED_DIMENSIONS set in
_dimension-scorers.ts and filter it out of all three averages. The
filter is keyed on the retired-dim REGISTRY, not on coverage === 0,
because a non-retired dim can legitimately emit coverage=0 on a
genuinely sparse-data country via weightedBlend fall-through — those
entries MUST keep dragging confidence down (that is the sparse-data
signal lowConfidence exists to surface). Verified: sparse-country
release-gate test (marks sparse WHO/FAO countries as low confidence)
still passes with the registry-keyed filter; would have failed with
a naive coverage=0 filter.

Server-client parity: widget-utils cannot import server code, so
RESILIENCE_RETIRED_DIMENSION_IDS is a hand-mirrored constant, kept
in lockstep by tests/resilience-retired-dimensions-parity.test.mts
(parses the widget file as text, same pattern as existing widget-util
tests that can't import the widget module directly).

P2 — false "Source down" label on retired dim
---------------------------------------------
scoreFuelStockDays hard-coded imputationClass: 'source-failure',
which the widget maps to "Source down: upstream seeder failed" with
a `!` icon for every country. That is semantically wrong for an
intentional retirement. Flipped to null so the widget's absent-path
renders a neutral cell without a false outage label. null is already
a legal value of ResilienceDimensionScore.imputationClass; no type
change needed.

Tests
-----
- tests/resilience-confidence-averaging.test.mts (new): pins the
  registry-keyed filter semantic for computeOverallCoverage +
  computeLowConfidence. Includes a negative-control test proving
  non-retired coverage=0 dims still flip lowConfidence.
- tests/resilience-retired-dimensions-parity.test.mts (new):
  lockstep gate between server and client retired-dim lists.
- Widget test adds a registry-keyed exclusion test with a non-retired
  coverage=0 dim in the fixture to lock in the correct semantic.
- Existing tests asserting imputationClass: 'source-failure' for
  fuelStockDays flipped to null.

All 494 resilience tests + full 6336/6336 data-tier suite pass.
Typecheck clean for both tsconfig.json and tsconfig.api.json.

* docs(resilience): align methodology + registry metadata with shipped imputationClass=null

Follow-up to the previous PR 3 review commit that flipped
scoreFuelStockDays's imputationClass from 'source-failure' to null to
avoid a false "Source down" widget label on every country. The code
changed; the doc and registry metadata did not, leaving three sites
in the methodology mdx and two comment/description sites in the
registry still claiming imputationClass='source-failure'. Any future
reviewer (or tooling that treats the registry description as
authoritative) would be misled.

This commit rewrites those sites to describe the shipped behavior:
 - imputationClass=null (not 'source-failure'), with the rationale
 - exclusion from confidence/coverage averages via the
   RESILIENCE_RETIRED_DIMENSIONS registry filter
 - the distinction between structural retirement (filtered) and
   runtime coverage=0 (kept so sparse-data countries still flag
   lowConfidence)

Touched:
 - docs/methodology/country-resilience-index.mdx (lines ~33, ~268, ~590)
 - server/worldmonitor/resilience/v1/_indicator-registry.ts
   (recoveryFuelStockDays comment block + description field)

No code-behavior change. Docs-only.

Tests: 157 targeted resilience tests pass (incl. methodology-lint +
widget + release-gate + confidence-averaging). Typecheck clean on
both tsconfig.json and tsconfig.api.json.
2026-04-22 23:57:28 +04:00

195 lines
9.8 KiB
TypeScript
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
import assert from 'node:assert/strict';
import { existsSync } from 'node:fs';
import { dirname, join } from 'node:path';
import { describe, it } from 'node:test';
import { fileURLToPath } from 'node:url';
import { INDICATOR_REGISTRY } from '../server/worldmonitor/resilience/v1/_indicator-registry.ts';
import {
RESILIENCE_DIMENSION_DOMAINS,
getResilienceDomainWeight,
type ResilienceDimensionId,
type ResilienceDomainId,
} from '../server/worldmonitor/resilience/v1/_dimension-scorers.ts';
// PR 3 §3.6 — Coverage-and-influence cap on indicator weight.
//
// Rule (plan §3.6, verbatim):
// No indicator with observed coverage below 70% may exceed 5% nominal
// weight OR 5% effective influence in the post-change sensitivity run.
//
// This file enforces the NOMINAL-WEIGHT half (static, runs every build).
// The effective-influence half is checked by the variable-importance
// output of scripts/validate-resilience-sensitivity.mjs and committed as
// an artifact; see plan §5 acceptance-criteria item 9.
//
// Why the gate exists (plan §3.6):
// "A dimension at 30% observed coverage carries the same effective
// weight as one at 95%. This contradicts the OECD/JRC handbook on
// uncertainty analysis."
//
// Assumption: the global universe is ~195 countries (UN members + a few
// territories commonly ranked). "70% coverage" → 137+ countries.
const GLOBAL_COUNTRY_UNIVERSE = 195;
const COVERAGE_FLOOR = Math.ceil(GLOBAL_COUNTRY_UNIVERSE * 0.7); // 137
const NOMINAL_WEIGHT_CAP = 0.05; // 5%
// Nominal overall weight of an indicator = weight in dimension
// × dimension share of domain
// × domain weight in overall score.
//
// `dimension share of domain` is NOT 1/N_total — the scorer aggregates
// by coverage-weighted mean (server/worldmonitor/resilience/v1/_shared.ts
// coverageWeightedMean), so a dimension that pins at coverage=0 drops
// out of the denominator and the surviving dimensions' shares go UP,
// not down. PR 3 commit 1 retires fuelStockDays by pinning its scorer
// at coverage=0 for every country — so in the current live state the
// recovery domain has 5 contributing dimensions (not 6), and each core
// recovery indicator's nominal share is 1/5 × 0.25 = 5%, not the
// 1/6 × 0.25 = 4.17% a naive N-based count would report.
//
// We therefore count "effective contributing dimensions" per domain:
// dimensions that have at least one tier='core' indicator in the
// registry. A dimension with only experimental/enrichment indicators
// (e.g. fuelStockDays, post-retirement) scores coverage=0 in the core
// path and is excluded from the coverage-weighted domain mean, so it
// does not dilute the core dimensions' shares.
//
// This still under-estimates the WORST case — a live source-failure
// run can drop a usually-contributing dimension to coverage=0, further
// raising surviving dimensions' shares. The worst-case upper bound is
// indicator.weight × domain_weight (single surviving dimension, 1/1
// share). Enforcing THAT bound would fail most indicators, so we
// enforce the baseline (all core-bearing dimensions present) here and
// rely on the sensitivity-script's effective-influence output (plan
// §3.6 second half, plan §5 acceptance item 9) to catch the dynamic
// case.
//
// Indicator weights within a dimension are normalized to sum to 1 for
// non-experimental tiers (enforced by the indicator-registry test).
function dimensionsInDomain(domainId: ResilienceDomainId): ResilienceDimensionId[] {
return (Object.keys(RESILIENCE_DIMENSION_DOMAINS) as ResilienceDimensionId[])
.filter((dimId) => RESILIENCE_DIMENSION_DOMAINS[dimId] === domainId);
}
function coreBearingDimensions(domainId: ResilienceDomainId): Set<ResilienceDimensionId> {
const dimsInDomain = new Set(dimensionsInDomain(domainId));
const withCore = new Set<ResilienceDimensionId>();
for (const entry of INDICATOR_REGISTRY) {
if (entry.tier === 'core' && dimsInDomain.has(entry.dimension)) {
withCore.add(entry.dimension);
}
}
return withCore;
}
function nominalOverallWeight(indicator: typeof INDICATOR_REGISTRY[number]): number {
const domainId = RESILIENCE_DIMENSION_DOMAINS[indicator.dimension];
if (domainId == null) return 0;
const domainWeight = getResilienceDomainWeight(domainId);
// Count only dimensions that have ≥1 core indicator — retired or
// all-experimental dimensions contribute coverage=0 to the scorer and
// are excluded from the coverage-weighted domain mean.
const contributing = coreBearingDimensions(domainId).size;
const dimensionShare = contributing > 0 ? 1 / contributing : 0;
return indicator.weight * dimensionShare * domainWeight;
}
describe('resilience coverage-and-influence gate (PR 3 §3.6)', () => {
it('no indicator with <70% country coverage carries >5% nominal weight in the overall score', () => {
const violations = INDICATOR_REGISTRY
// Only core indicators contribute to the overall (public) score.
// Enrichment and experimental are drill-down-only, so their
// nominal-weight-in-overall is 0 regardless of registry weight.
.filter((e) => e.tier === 'core')
.filter((e) => e.coverage < COVERAGE_FLOOR)
.map((e) => ({
id: e.id,
dimension: e.dimension,
coverage: e.coverage,
weight: e.weight,
nominalOverall: Number(nominalOverallWeight(e).toFixed(4)),
}))
.filter((v) => v.nominalOverall > NOMINAL_WEIGHT_CAP);
assert.deepEqual(
violations,
[],
`Indicators below ${COVERAGE_FLOOR}-country coverage floor with nominal overall weight > ${NOMINAL_WEIGHT_CAP * 100}%:\n${
violations.map((v) => ` - ${v.id} (dim=${v.dimension}, coverage=${v.coverage}, nominal=${(v.nominalOverall * 100).toFixed(2)}%)`).join('\n')
}\n\nFix options:\n 1. Demote to enrichment or experimental tier.\n 2. Lower the indicator's weight within its dimension.\n 3. Improve coverage to ≥${COVERAGE_FLOOR} countries.`,
);
});
it('effective-influence artifact reference exists (sensitivity-script contract)', () => {
// The plan (§3.6, §5 item 9) requires post-change variable-importance
// to confirm the nominal-weight gate is not violated in the dynamic
// (variance-explained) dimension either. That artifact is produced
// by scripts/validate-resilience-sensitivity.mjs and not re-computed
// here (it requires seeded Redis). This test only asserts the gate
// script exists, so removing it via refactor breaks the build.
const here = dirname(fileURLToPath(import.meta.url));
const sensScript = join(here, '..', 'scripts', 'validate-resilience-sensitivity.mjs');
assert.ok(existsSync(sensScript),
`plan §3.6 effective-influence half is enforced by ${sensScript} — file is missing`);
});
it('retired dimensions (coverage=0 for every country) do not count in the per-domain share denominator', () => {
// Regression guard for the §3.6 gate math. When PR 3 commit 1
// pinned fuelStockDays at coverage=0, the coverage-weighted domain
// aggregation raised the surviving recovery dimensions' shares from
// 1/6 to 1/5. Any gate that uses 1/N_total as the divisor will
// under-report nominal influence and can silently pass a regression
// that drives a low-coverage indicator above the 5% cap.
//
// This test asserts the helper correctly excludes all-experimental
// dimensions from the share denominator.
const recoveryDimsTotal = dimensionsInDomain('recovery').length;
const recoveryCoreBearing = coreBearingDimensions('recovery').size;
assert.ok(recoveryCoreBearing < recoveryDimsTotal,
`expected at least one recovery dimension to be all-non-core (post-fuelStockDays-retirement); got ${recoveryCoreBearing}/${recoveryDimsTotal}. If this flips, the fuelStockDays retirement was reverted and §3.6 math assumptions need review.`);
// Explicit: fuelStockDays is the dimension we retired. Confirm it
// has zero core indicators.
const fuelStockCoreCount = INDICATOR_REGISTRY.filter(
(e) => e.dimension === 'fuelStockDays' && e.tier === 'core',
).length;
assert.equal(fuelStockCoreCount, 0,
'fuelStockDays must have zero core indicators post-PR 3 §3.5 retirement. If this fails, un-retire must be intentional + the gate math reviewed.');
// And the recovery-domain core indicators should each compute 5%
// under the corrected formula (1.0 × 1/5 × 0.25), not 4.17%.
const debtToReserves = INDICATOR_REGISTRY.find((e) => e.id === 'recoveryDebtToReserves');
assert.ok(debtToReserves != null, 'recoveryDebtToReserves must exist');
const computed = nominalOverallWeight(debtToReserves!);
// 0.05 exactly, allow fp wiggle
assert.ok(Math.abs(computed - 0.05) < 1e-9,
`recoveryDebtToReserves nominal weight should be 0.05 (1.0 × 1/5 × 0.25) post-retirement; got ${computed}. If this is 0.0417, the share denominator is using 1/6 instead of 1/5 — fuelStockDays retirement is not being excluded.`);
});
it('reports the current nominal-weight distribution for audit', () => {
// Visibility-only (no assertion beyond "ran cleanly"). The output
// lets reviewers eyeball the distribution and spot outliers that
// technically pass (coverage ≥ floor) but still carry unusually
// high weight for a narrow construct.
const ranked = INDICATOR_REGISTRY
.filter((e) => e.tier === 'core')
.map((e) => ({
id: e.id,
nominalOverall: Number((nominalOverallWeight(e) * 100).toFixed(2)),
coverage: e.coverage,
}))
.sort((a, b) => b.nominalOverall - a.nominalOverall)
.slice(0, 10);
if (ranked.length > 0) {
console.warn('[PR 3 §3.6] top 10 core indicators by nominal overall weight:');
for (const r of ranked) {
console.warn(` ${r.id}: nominal=${r.nominalOverall}% coverage=${r.coverage}`);
}
}
assert.ok(ranked.length > 0, 'expected at least one core indicator');
});
});